deno_std icon indicating copy to clipboard operation
deno_std copied to clipboard

How to build the library so to obtain the same artifacts which were on npm up to last week

Open 6xrS42VaMBgMbWRPAiVP opened this issue 1 month ago • 1 comments

Hello, I'm currently testing a node module which depends on the now not-existing @jsr/std__path on npm.

In particular the module seem to require the common javascripts files which can be found in the npm artifacts for that package, which I have re-published as @themartiancompany/std__path because I didn't get how I'm supposed to properly generate them.

So I suppose I should have called the issue 'missing build instructions' but i imagine we can do that later.

6xrS42VaMBgMbWRPAiVP avatar Nov 06 '25 22:11 6xrS42VaMBgMbWRPAiVP

I'm currently testing a node module which https://github.com/JiangJie/happy-opfs/issues/5 on the now not-existing @jsr/std__path on npm.

@jsr/std__path still exists in jsr backed custom npm registry https://npm.jsr.io/ . Check this url https://npm.jsr.io/@jsr/std__path

You need to set up .npmrc file with the following content to install it:

@jsr:registry=https://npm.jsr.io

This forwards @jsr/ scope to npm.jsr.io.

(Note: this file is automatically created when you execute npx jsr add <jsr_package> command)

kt3k avatar Nov 14 '25 05:11 kt3k