-
-
Notifications
You must be signed in to change notification settings - Fork 33.5k
sea: use JSON configuration and blob content for SEA #47125
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
Conversation
Review requested:
|
0f67d94
to
c43ae7c
Compare
Updated the documentation a bit, still needs to write a bunch of tests... |
8654fbd
to
807b866
Compare
Added tests and documentation. @nodejs/single-executable PTAL thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👏🏼 Awesome
Landed in 491a5c9 |
@joyeecheung should this be labelled as a
notable-change
|
The
notable-change
Please suggest a text for the release notes if you'd like to include a more detailed summary, then proceed to update the PR description with the text or a link to the notable change suggested text comment. |
Good idea. Done. |
FYI @joyeecheung: Originally posted by @RafaelGSS in #47381 (comment)
Should we add some release notes for this change? |
This implements the ideas discussed in nodejs/single-executable#58. This changes the SEA contract in that:
--experimental-sea-config
), this makes it possible to include other resources into the SEA other than just the JS code--experimental-sea-config
) which allows for more flexibility.Refs: nodejs/single-executable#58