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

[feat] Make backend js ecosystem future better #20919

Closed
loynoir opened this issue Oct 16, 2023 · 1 comment
Closed

[feat] Make backend js ecosystem future better #20919

loynoir opened this issue Oct 16, 2023 · 1 comment

Comments

@loynoir
Copy link

loynoir commented Oct 16, 2023

Feature Request

Make backend js ecosystem future better.

What changed?

Program language like rust and zig, leads to new backend js/ts runtime like deno and bun.

What is the problem?

npm is awesome.

To use awesome npm package for backend, usually need Node.js core module.

But, currently, because three runtime not able to share same Node.js core module, when use deno or bun with npm packages, there are compatibility issues.

Because Node.js deno bun does not able to share same Node.js core module and spec and test, deno bun reinvent the not-fully-compact wheel individually, and not reinvent-once-use-forever.

What maybe the solution?

Node.js deno bun all support napi.

Extra

I don't know if override core module is needed for solution.

If it does, I guess Node.js loader and deno importmap should works.

What is the feature request?

  • Rewrite Node.js core module using napi

  • Rewrite Node.js core module test using javascript, so Node.js deno bun browserify-XXX can share SAME test

  • Publish napi version of Node.js core module to npm

  • Maybe publish to npm under a new organization @backend-javascript-core-module-standard-committee/http

Related

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

2 participants