-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ESM Modules not supported #16
Comments
What's the error you see on console when you run the app? I have axios too in my project and using that solution works for me |
In my case I get these errors to begin with:
then it continues with the same errors as before:
and so on... |
I suggest to try pre-building your application using es-build and then pkg against the single file bundle. Otherwise if you are able to spot the error feel free to submit a PR |
Let's use this issue for all the others. Seems that starting from nodejs 18.19.0 and for all nodejs 20+ versions some modules that support both esm and cjs are not bundled correctly. This is IMO due to resolve package that is not able to correctly parse package.json Let's use this issue as a tracker for such issues instead of having multiple open ones. The error will look like:
Alternative solutionsBelow some solutions I tried and other possible working ones Using
|
The only approach that finally worked for me was to use esbuild, but it was still a huge undertaking, as my project is quite large an complex... |
@manast tried |
This may fix all those issues: nodejs/node#51977 (comment) Ref: https://joyeecheung.github.io/blog/2024/03/18/require-esm-in-node-js/ |
That's really exciting news, but I've already given up on using pkg with ESM because I wanted to support the import syntax in the VM and use the latest packages. It looks like I can go back to pkg now? |
@luckyyyyy not yet there is still not an available nodejs lts version with that and I need to play with it a bit |
My issueI've been trying for a while to resolve this issue, as I'm stuck behind without the option to add some modules that shipped with the My
|
While still not an ideal solution, I had similar issues upgrading from Node 18 to Node 20 and was able to get basic support for a pkg built executable with native node modules, embedded C++ binaries, and other JS dist assets bundled and functioning with minimal effort using #10 (comment) I still agree that for existing known mitigations, refactoring to use ESBuild may prove to be a better long term tactic. |
Just wanted to let you all know that we have a successful usage of esbuild with PKG and node 20 in https://github.com/MatrixAI/Polykey-CLI - it even has native binaries involved and nix involved (all in flake.nix). |
Thanks for sharing 🙏 Any description of how? |
Hey there, following the post of @CMCDragonkai I also tried to move our CLI to use ESM with esbuild (on node18). I could manage to get the full flow working, including with native librairies. The build script is pretty similar to the one in Polykey: https://github.com/Dashlane/dashlane-cli/blob/master/scripts/build.js I could use One caveat I encountered is that esbuild is not transpiling the dynamic imports If you have time to take a look, I'm really looking for feedback :) |
Check this evanw/esbuild#2651. |
And this evanw/esbuild#700 regarding dynamic imports. |
What version of pkg are you using?
5.11.1
What version of Node.js are you using?
16.19.1
What operating system are you using?
macOS
What CPU architecture are you using?
x86_64
What Node versions, OSs and CPU architectures are you building for?
node16-macos-x64
Describe the Bug
This issue is mentioned in the original package, but the package is archived, then I found a solution in issue's comment:
vercel#1936
But it still does not work
Expected Behavior
Compile app without axios (lastest version) error
To Reproduce
A Project that include the lastest version of axios (e.g: v1.6.4)
The text was updated successfully, but these errors were encountered: