dfx generate seems to assume everyone is using webpack which is not the case. I am having to do add custom hacks into my workflow to get around the assumption of webpack, as I am using vite. Look at this code: import { Actor, HttpAgent } from "@dfinity/agent"; // Imports and re-exports candid int…

Actually I still haven’t gotten this to work yet, here’s a related issue: Global is not defined

Fair feedback, let me pass to SDK folks

we’ve been slowly trying to remove the webpack tentacles from dfx. we discussed some possible options as a team earlier. here is what we’re thinking: we will provide a configuration that dfx generate will use to determine how to define / insert canister IDs at build time. this may be called env_co…

You could consider creating the process object if it doesn’t exist, that was the main problem I had. Also the global object could not be found, you could consider creating that if it doesn’t exist. These have been simple enough for me to polyfill, but it’s sad that it just breaks in esoteric ways t…

There’s a problem in the non-node-compatible generated code, which is that it calls createActor during initialization of the module. This means that the developer cannot insert their own settings into the agent, meaning that if a browser app wants to serve from a different domain then they can’t use…

It seems that no combination of URLs in the browser, in the HttpAgent settings for the client, deploying to a canister or running a standalone server, etc that I’ve tried can give me a consistent working agent.

In Juno, which uses Vite, I set the "node_compatibility": true in dfx.json and then use a script ( https://github.com/buildwithjuno/juno/blob/main/scripts/update.types.mjs ) to clean the types that are automatically generated. That way I keep only what’s needed, what compiles and I create my own facto…

I found a solution to my problems as described more here: Dfx generate fetchRootKey broken with vite - #25 by lastmjs

That being said, I have decided to simply deploy my frontend as a frontend canister. Trying to run a separate frontend server seemed to be causing lots of issues, and I would love to see those addressed, but I’ve moved on from that problem for now. Ideally a frontend deployed to a canister and runn…

Dfx generate assumes too much

Developers

lastmjs May 22, 2023, 10:00pm 4

Another potentially related issue: Dfx generate fetchRootKey broken with vite

Topic		Replies	Views
Dfx generate fetchRootKey broken with vite Developers	26	1167	February 15, 2024
Generated declarations in Node.js environment break Developers	28	2222	September 1, 2022
Creating a web canister Developers	33	1585	June 20, 2023
Vite.js apps with dfx 0.8.1? Developers	3	1208	September 27, 2021
Dfx .env incorrect canister ids generated? Developers	16	1264	October 24, 2024

Dfx generate assumes too much

Related topics