Unpin deno_std dependencies
See original GitHub issueI’m not suggesting to disregard the deno_std version altogether, but ass of right now - without #19 -oak
is incompatible with the latest version of Deno because all deps are pinned to v0.9.0. Obviously there are major benefits to having releases pinned to the Deno runtime version it was developed for, but it would be nice to at least have a version of oak
without the dependencies pinned to a specific Deno version.
This could be in the form of the master
branch or a latest
/unpinned
tagged release that keeps getting updated.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6
Top Results From Across the Web
Unpin every dependency · Issue #3186 · web3/web3.js - GitHub
This project has lots of pinned dependencies (i. e. exact version defined in the dependencies entries). This is not good in a library...
Read more >How should you pin dependencies and why? – The Guild
With the term pinning we are referring to the practice of making explicit the version of the libraries your application is depending on....
Read more >Should you Pin your JavaScript Dependencies?
The pros and cons of dependency pinning for JavaScript/npm. ... If instead you "pin" your dependencies rather than use ranges, it means you...
Read more >is-promise Post Mortem : r/programming - Reddit
Those downloads came because their dependencies were unpinned. The people who left the dependencies unpinned likely did not actively intend to do so....
Read more >danbev/learning-rust - Github Plus
Unpin `, which is `dereferenceable` but neither `noalias` nor `readonly`. ... Check file:///home/danielbevenius/work/deno/deno/std/examples/welcome.ts ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I guess I could keep master unpinned and when when we cut a release, pin it. I have been tagging releases with updates.
Not with the way the changes break at this stage. Sometimes it is just
deno_std
<-> Deno, sometimes it is something indeno_std
<->oak
, sometimes it is Deno <->oak
. 🤷♂ Also sometimes Ry isn’t tagging adeno_std
release quickly after a Deno release, and so sometimes upgrading is hard. I think when things get more stable…BTW, the std update pull has been moved into it’s own branch so the pull is now #19.