The convenience of Deno is that you put directly the GitHub URL of the repo. Which means that instead of knowing the package name you have to know its full URL (https://github.com/encode/django-rest-framework vs djangorestframework by example) but also if the project moves then you have to change the URL. And of course since the version of the package is in the URL, you have to know the version you're using all over the place (and change it when you upgrade).
Did I mention that Deno is so usable that its website is made with Node?
Dammn isn’t that hard. Like every time the repo has some breaking changes and since we link with url in the code won’t that break our application 🤯
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The convenience of Deno is that you put directly the GitHub URL of the repo. Which means that instead of knowing the package name you have to know its full URL (
https://github.com/encode/django-rest-frameworkvsdjangorestframeworkby example) but also if the project moves then you have to change the URL. And of course since the version of the package is in the URL, you have to know the version you're using all over the place (and change it when you upgrade).Did I mention that Deno is so usable that its website is made with Node?
It is probably better to add tag or commithash as well.
So,
https://github.com/encode/django-rest-framework@3.9.3, or something. I haven't tested.Dammn isn’t that hard. Like every time the repo has some breaking changes and since we link with url in the code won’t that break our application 🤯