Repository navigation
Replies: 3 comments
|
Good idea, and it fits the git-source model. I opened #15461. An [tools."npm:https://pkg.pr.new/kjanat/actionlint/@kjanat/actionlint@343"]
version = "latest"
allow_exotic_deps = trueSince the URL has no version list, One difference from your proposal: the package is installed under the last path segment of the URL ( AI-assisted — Tool: Claude Code; model: anthropic/claude-sonnet-5-5; version: 2.1.317. |
|
Update after review and testing against the real
AI-assisted — Tool: Claude Code; model: anthropic/claude-sonnet-5-5; version: 2.1.317. |
|
One more correction to my last comment: AI-assisted — Tool: Claude Code; model: anthropic/claude-sonnet-5-5; version: 2.1.317. |
Uh oh!
There was an error while loading. Please reload this page.
pkg.pr.new publishes preview npm packages for every push to a PR and posts install commands as tarball URLs (example comment):
I'd like to install such a URL with the npm backend. Every form I tried fails on mise 2026.11.3:
Proposal
Accept an
https://tarball URL as an npm source, the way #14044 added git sources:namein the tarball'spackage.json.latestmeans the tarball the URL serves now;@343serves the newest push to PR 343.optionalDependenciesare pkg.pr.new URLs pinned to the commit ("@kjanat-actionlint/actionlint-linux-x64": "https://pkg.pr.new/.../actionlint-linux-x64@7fb70dc5..."), so they still go throughallow_exotic_deps.mise.lockcan record the tarball's integrity as it does for git and registry sources.#14896 rejects URLs in the version field to keep untrusted values out of package specs. A URL in the tool name is declared the same way a git source is.
Workaround
The
httpbackend installs the per-platform binary package directly:This only works for packages that ship one binary per platform, and the URL template has to repeat the package's platform naming.
All reactions