-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Feature/request Deno package management just like npm #5832
Comments
There are two patterns you can follow to control versions of external modules in a single file. The first is through the use of import maps, while the second is a pattern of using For updating dependencies, checkout udd which can update all your dependencies with a rule based approach. |
@Mohsin51 The Deno is build to solve the existing problems from NodeJS like having a central authority like npm, having package.json, etc. You can watch the video mentioning all these things https://www.youtube.com/watch?v=M3BM9TB-8yA |
Outside of scope of Deno |
I've created make-deno-edition to make npm packages written in typescript compatible with deno - is working on badges - usage proof of this here https://repl.it/@balupton/badges-deno - has been used now to make 32 node packages compatible with deno - you can use project to automatically generate the readme instructions for the deno edition - and can use boundation to automatically scaffold your projects to automate the entire process - start-of-week is an example where different entries are used for node, deno, and web browsers |
Deno community is against introducing anything similar to package.json but I am not sure if their approach is better. It's difficult to manage/import packages with absolute URL, there should be something like package.json which gives you details and ability to control versions of external modules which your application is using in single file. Need some sort of cli as well like npm i package@latest.
Not sure how to restrict or bring latest version of package .
Dockerizing Deno application seems confusing at this point.
The text was updated successfully, but these errors were encountered: