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

Support Deno #64

Open
alexgleason opened this issue Sep 9, 2024 · 2 comments
Open

Support Deno #64

alexgleason opened this issue Sep 9, 2024 · 2 comments

Comments

@alexgleason
Copy link

  • Deno does not have a package.json. It has an optional deno.json.
  • Deno does not create a node_modules directory alongside each project. It downloads modules into ~/.cache/deno/deps.
  • Deno CAN use packages from npm, jsr, and https. It can use multiple sources within the same project.

Need to explore other ways package maintainers can add funding metadata to their packages. Maybe https imports will never work, but it should be possible to make it work with both npm and jsr packages on Deno.

@bumi
Copy link
Contributor

bumi commented Sep 11, 2024

nice, thanks for the issue!
would be awesome to support Deno!

what are your thoughts on pkgzap? we haven't managed to get enough attention so far on the concept

@alexgleason
Copy link
Author

I think it's a great idea, held back only by Bitcoin and Lightning itself not being as ubiquitous as it should.

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