-
Notifications
You must be signed in to change notification settings - Fork 1k
Unable to compile app with -r esm #954
Comments
Hey @acidos, I'm getting the same error when running |
@hasparus no, I gave up... |
I had the same issue and it was only happening when I ran it from the terminal in VSCode. In a separate terminal it worked. (Changing the shell in VSCode didn't help either). |
It seems NODE_OPTIONS is read by the In my case, that NODE_OPTIPONS was in my particular environment defined by VSCode because I was debugging on that moment. I don't know the reason because I saw some errors related to that: Another example of this, on this issue in graphql-engine, solved removing the environment variable. I don't know if vercel/pkg/@igorklopov want to remove this feature, because it could be useful. However, I will make a PR to include it on the documentation. |
closing duplicate of #782 |
Production binaries shall NOT take NODE_OPTIONS from end-users. Only the users (developers who use pkg to package their project) should have control over the flags via the "bake in" (--options) mechanism. Bug: vercel/pkg#954, vercel/pkg#989, vercel/pkg#1194, vercel/pkg#1517
Production binaries shall NOT take NODE_OPTIONS from end-users. Only the users (developers who use pkg to package their project) should have control over the flags via the "bake in" (--options) mechanism. Bug: vercel/pkg#954, vercel/pkg#989, vercel/pkg#1194, vercel/pkg#1517
Production binaries shall NOT take NODE_OPTIONS from end-users. Only the users (developers who use pkg to package their project) should have control over the flags via the "bake in" (--options) mechanism. Bug: vercel/pkg#954, vercel/pkg#989, vercel/pkg#1194, vercel/pkg#1517
I am using
esm
module for running my app. This is how I ran it.Now when I try to compile my app using pkg with the following line
I am getting the following errors for every file
The text was updated successfully, but these errors were encountered: