Skip to content
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

Roadmap #5

Open
rightaway opened this issue Oct 10, 2023 · 16 comments
Open

Roadmap #5

rightaway opened this issue Oct 10, 2023 · 16 comments

Comments

@rightaway
Copy link

Is there a roadmap for the fork short term and long term?

Node 20
https://github.com/vercel/pkg-fetch/issues/302

ESM
vercel#1291
https://github.com/vercel/pkg/discussions/1388
vercel#1655
vercel#1323

Multiple entry points
vercel#481

XDG directory
vercel#1225

Sharp
vercel#1918

@robertsLando
Copy link
Member

No roadmap here, I just started this to allow users contributing to the code and give the project a new life. Do you want to help?

@CMCDragonkai
Copy link

We'd definitely like to help. Right now we used to use pkg without a pre-existing bundler, but I think it would be better to simply get users to always use a bundler first like esbuild, then use pkg. It would simplify pkg.

@robertsLando
Copy link
Member

Yeah I think that including the pre-bundling inside pkg makes no sense, I would instead write better docs about that process and maybe add examples too

@rightaway
Copy link
Author

That will modify stack traces which makes hard to track errors in production. Stack traces with original file names and line numbers are critical and bundling shouldn't be expected by users.

Important thing is to see if someone has expertise to make native ESM support possible.

@CMCDragonkai
Copy link

The lack of bundling results in pkg packaging everything include README.md, LICENSE.md files into the executable.

@robertsLando
Copy link
Member

robertsLando commented Oct 19, 2023

Important thing is to see if someone has expertise to make native ESM support possible.

The only one that has the ability to do it (that I know) was @jesec but I didn't heard him from a long time, I know he also had something working with ESM but never finished the implementation.

The future of packaged nodejs apps is Node SEA, Deno and/or Bun IMO once one of this 3 "native" methods become more usable. My goal in the meanwhile is to keep pkg as much updated as possible and give the possibility to the ones that would like to contribute to see their PR merged and not to stay there for years without any response...

Pkg is so hard to maintain only due to the need of building nodejs patches, if in the future we could ever get rid of them that would be awesome but I don't think if it would be ever possible... Also the releases process is complicated and I took some time to write it down on docs: https://github.com/yao-pkg/pkg-fetch/blob/main/DEVELOPMENT.md

@rightaway
Copy link
Author

The lack of bundling results in pkg packaging everything include README.md, LICENSE.md files into the executable.

pkg documentation says it can build the executable without sources.

The future of packaged nodejs apps is Node SEA, Deno and/or Bun IMO once one of this 3 "native" methods become more usable.

These methods will include sources.

@robertsLando
Copy link
Member

@rightaway Node SEA compiles code in V8 bytecode like pkg does

@rightaway
Copy link
Author

I read will be possible to see source in SEA bundle. Documentation don't mention bytecode do you know where you read it?

@rightaway
Copy link
Author

pkg is deprecated and they said there were active forks does anyone know which are the most active?

@Infern1
Copy link

Infern1 commented Jan 4, 2024

seems this one is the most active for now

@robertsLando
Copy link
Member

This one is the most active

@jerrygreen
Copy link

I wish Node v20 to be supported 😢

SEA is still early beta, with just basic features, pkg seemed like more production-ready approach.

@robertsLando
Copy link
Member

Lol it is from at least 2 months now 🤣

@dingiyan
Copy link

dingiyan commented Apr 5, 2024

Thank you for your branch contribution. I really like and need it.
When I learned that the official pkg was no longer being maintained, I was saddened because SEA was not yet fully developed and convenient to use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants