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] some really big ideas about future deno registry #331

Open
loynoir opened this issue Jan 30, 2023 · 0 comments
Open

[feat] some really big ideas about future deno registry #331

loynoir opened this issue Jan 30, 2023 · 0 comments

Comments

@loynoir
Copy link

loynoir commented Jan 30, 2023

Actual: node.js

In node.js ecosystem

https://github.com/verdaccio/verdaccio

  • self-hostable, can be a private npm registry
  • can proxy cache package from multiple public npm registry
  • have dockerhub image, very easy to install

https://github.com/ije/esm.sh

  • make public/private npm package available in browser import(), or said the bridge convert node-js-cjs node-js-esm code to browser-js-esm
  • auto browserify, eg, convert fs.promises.writeFile to memfs.promises.writeFile when browser detected

Expected: deno

Some really big ideas about future deno registry

Compared with verdaccio

  • make it self-hostable, be able to act as private deno registry. Seems not self-hostable yet
  • proxy cache public package
  • provide dockerhub image

Compared with esm.sh

  • deno use deno-ts-esm code, browser use browser-js-esm code
  • auto browserify, eg, convert Deno.writeFile to equivalent memfs.promises.writeFile when browser detected
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

1 participant