question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Allow semver ranges and identifiers in urls

See original GitHub issue

The website should be able to resolve semver symbols. Being able to use semver to dedupe dependencies is an important step towards facilitating the development of medium to large web apps using Deno. I believe some other github redirectors already support this as well. While we could use those CDNs instead, the deno.land registry is currently the only place that exclusively lists deno modules. It may be possible to build further deduping tools once basic semver support is in place.

Some examples of what URLs would look like: https://deno.land/std@^0.50.0/path/mods.ts https://deno.land/std@~0.50.0/path/mods.ts https://deno.land/std@>=0.50.0/path/mods.ts https://deno.land/std@0.49.0||^0.51.0/path/mods.ts https://deno.land/std@0.49.0-0.51.0/path/mods.ts

Issue Analytics

  • State:open
  • Created 3 years ago
  • Reactions:4
  • Comments:16 (5 by maintainers)

github_iconTop GitHub Comments

5reactions
KnorpelSenfcommented, Apr 25, 2021

https://github.com/EdJoPaTo/deno-semver-redirect (written in Rust) solves this problem already by wrapping deno.land/x.

For instance, https://dsr.edjopato.de/grammy/0.x/mod.ts will parse the semver specifier and then redirect you to the correct latest 0.x version on deno.land/x, so you can use these URLs in import specifiers.

2reactions
wperroncommented, Aug 16, 2021

@tani I took a quick look at your project over the weekend, it looks interesting! I wouldn’t be against merging it if you want to open a PR implementing it on this repo. the deno.land website is already running on Deploy so it should be pretty easy. One thing I would want to see on that PR though would be unit tests; Your implementation seems to work using Regex and I would want to be sure that it works as expected before merging it.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Allow semver ranges and identifiers in urls · Issue #606 - GitHub
The website should be able to resolve semver symbols. Being able to use semver to dedupe dependencies is an important step towards ...
Read more >
Semantic Versioning 2.0.0 | Semantic Versioning
Build metadata MAY be denoted by appending a plus sign and a series of dot separated identifiers immediately following the patch or pre-release...
Read more >
package.json - npm Docs
Dependencies are specified in a simple object that maps a package name to a version range. The version range is a string which...
Read more >
Semantic Versioning - Devopedia
SemVer ranges specify allowed versions of each dependency. Source: Van de Moere 2013. SemVer ranges specify allowed versions of each dependency.
Read more >
PEP 440 – Version Identification and Dependency Specification
As the Python Package Index is intended solely for indexing and hosting upstream projects, it MUST NOT allow the use of local version...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found