-
Notifications
You must be signed in to change notification settings - Fork 1k
Pkg: FLAGS_MISMATCH when I run the packaged app. #484
Comments
Ran into this when I added |
you may also check if there is NODE_OPTIONS environment variable set |
@hshixun Thanks, will check that var next time. |
Running into this over at https://github.com/lando/lando We compile lando with Is there a way to compile |
Any update on this? Seems like an enormous bug... anyone with the It also seems easy to fix. Can pkg simply clear the |
I'm keen for an update, too. Having to |
This is breaking my balls as well. |
Lol this is stupid. It seems to work if you compile it with options though e.g. pkg . --options max_old_space_size=4096 |
It really doesn't seem like the solution should be to set every possible option in Is there some reason the current environment can't be detected and override whatever |
Revising my initial suggestion, could the bundled binary simply invoke |
This issue is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 5 days. To ignore this issue entirely you can add the no-stale label |
Anyone with the |
This issue is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 5 days. To ignore this issue entirely you can add the no-stale label |
This issue is now closed due to inactivity, you can of course reopen or reference this issue if you see fit. |
With latest Node 16, the binary built with pkg exits immediately. We have no warning "Pkg: FLAGS_MISMATCH".
It works if you unset NODE_OPTIONS env:
I leave this comment mainly to help users to find the solution, hoping search engines will guide them here 🙂. |
Can someone with pkg experience help us understand: Is this an easy fix? i.e. can pkg simply pass |
I spent like 5ish hours today trying to figure this out and I'm glad you all verified I'm not crazy haha. My goal was to dynamically set the heap size based on some bash-fu aimed at exporting NODE_OPTIONS. @jchook thanks for keeping this alive, maybe there's a fix by now 🤞 haha. |
@marquiswashere maybe open another ticket to get their attention. This seems to me like it should be easy to fix. |
It's most likely some misunderstanding on my side since I did not find any information of this by googling and searching the issues here.
Every time I run the packaged app, I got the warning:
I tried only using a index.js file with only the argv print operation.
Run
And run the packaged app, still the same result.
My node version: v10.7.0. pkg version is 4.3.3.
The text was updated successfully, but these errors were encountered: