Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Experiment: node-sea #39

Closed
arcanis opened this issue Sep 20, 2022 · 2 comments
Closed

Experiment: node-sea #39

arcanis opened this issue Sep 20, 2022 · 2 comments

Comments

@arcanis
Copy link
Contributor

arcanis commented Sep 20, 2022

Since the action item of the previous meeting was to build SEA experiments, I built mine: node-sea.

It generates JS files that, when required or executed from the CLI, either re-export a module or run a binary. It uses the Yarn libraries in order to generate the dataset that can be stored, and applied at runtime as a layer on top of the filesystem.

Note that you'll currently need to build the node binary from sources (nodejs/node#44537 is required), and some binaries such as Webpack will require nodejs/node#44732 for workers to be supported.

npx node-sea -c 'npm add prettier' -b prettier -m prettier -o prettier
~/node/node ./prettier.cjs --help
@jviotti
Copy link
Member

jviotti commented Sep 20, 2022

Amazing stuff @arcanis ! I'm making a note to take a deeper look into it soon. How are you embedding the generated JS code into the binary?

@jviotti
Copy link
Member

jviotti commented Sep 20, 2022

Also, let me convert this issue into a GitHub Discussion on the "Show and Tell" category!

@nodejs nodejs locked and limited conversation to collaborators Sep 20, 2022
@jviotti jviotti converted this issue into discussion #40 Sep 20, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants