Last 12 weeks · 0 commits
3 of 6 standards met
Repository: denoland/dnt. Description: Deno to npm package build tool. Stars: 1317, Forks: 46. Primary language: Rust. Languages: Rust (55.4%), TypeScript (44.5%), JavaScript (0.1%). License: MIT. Latest release: 0.42.3 (7mo ago). Open PRs: 8, open issues: 104. Last activity: 7mo ago. Community health: 50%. Top contributors: dsherret, Gaubee, g-plane, UrielCh, kt3k, hyp3rflow, rojvv, char, ah-yu, utajum and others.
As best as I can tell, this should be the correct mapping: To map an import like this to an npm package: But it does not work: Similarly it does not work with: I also tried many other variants in , but no luck: Same Same : Errors out saying it couldn't find file:///... For some reason it seems it does not find the imports to replace, like it must be doing when it rewrites to use the directory. Am I doing something wrong? I found some seemingly related issues and pull requests, but it's unclear if it's the same issue, or what the status on it is: https://github.com/denoland/dnt/issues/404 https://github.com/denoland/dnt/pull/398 https://github.com/denoland/dnt/pull/411
This PR updates the function in to correctly extract version numbers from JSR URLs, as mentioned in the issue #481 , in addition to the existing Deno Land URLs. The regex has been modified to match both /dnt@version/ (legacy) and /@deno/dnt/version/ (JSR) patterns. Previously, when dnt was imported from JSR, would always return "dev" because the URL format wasn't recognized. Now it properly extracts the version (e.g., "1.2.3") from JSR URLs like https://jsr.io/@deno/dnt/1.2.3/mod.ts. Testing: All existing tests pass New test validates JSR URL version extraction Full test suite runs successfully (except for unrelated yarn dependency test as i havent downloaded yarn, still if issues came up, i will check that too.)