add run subcommand

[ry]

npx jsr run @luca/flag

just like deno run jsr:@luca/flag

@JLarky https://twitter.com/JLarky/status/1783147968251748624

[kt3k]

Currently jsr run subcommand is used for running run-script in package.json. ref

jsr-npm/src/bin.ts

Line 56 in 4f1544c

["run <script>", "Run a script from the package.json file"],

Does it make sense to change the behavior conditionally based on the given argument? (Or should we replace the existing behavior?)

[opeolluwa]

what does the run command do, exactly? Suppose I have a module with a default export someFunction(){}

Will it exec the some function, and pass the argument to it if any?

[marvinhagemeister]

Right now it only runs scripts defined in package.json.

[opeolluwa]

Oh, okay

[opeolluwa]

I'm looking forward to working on this, I'm going to need more explanation of the feature request

[JLarky]

With npm packages I can run commands like prettier without installing the package using commands like npx, bunx or yarn dlx, pnpm dlx. I wish there was a way to run jsr packages in node/bun like we have with "deno run"

[jordanbtucker]

I wish there was a way to run jsr packages in node/bun like we have with "deno run"

This will likely require buy in from npm and bun. You can get half way there with npm using a .npmrc with JSR as a scoped registry.

For example:

# This works
deno run jsr:@denorg/scrypt/cli hash mypassword

# This fails
npx @jsr/denorg__scrypt/cli hash mypassword

# This also fails
npx @jsr/denorg__scrypt hash mypassword

This is because npm expects @jsr/denorg__scrypt/cli to be a directory with a package.json file since it needs to check that for a bin field.

If you remove the cli part, then npm is able to find the package.json file that JSR generated, but it does not have a bin field, so npm doesn't know what file to run.

bunx doesn't even get as far as recognizing the scoped registry even though bun add does.

[jordanbtucker]

I suppose it might be possible for jsr to do an npm install into a cache location and then run the requested file.

jsr run @denorg/scrypt/cli hash mypassword

# Under the hood, jsr does something like this:
export NPM_PREFIX=~./jsr
npm install @jsr/denorg__scrypt
node $NPM_PREFIX/@jsr/denorg__scrypt/cli hash mypassword

I don't think that's really within the scope of JSR since it's not a runtime itself.

The better solution is for npx and bunx to support JSR packages.

[nakasyou]

I tried to support this, but npm.jsr.io doesn't exports a main field in package.json so I couldn't complete to implement.
Probably, if you use npx to implement this, JSR have to export a main field in package.json in tarball.

[alexgleason]

This feature is important for AI tooling.

I created an MCP server with Deno and published it to JSR, but users have to install Deno to use it: https://gitlab.com/soapbox-pub/nostr-mcp#installation

So I still need to publish it to npm to make it accessible to everyone.

[alexgleason]

It looks like this gets close:

npx --registry=https://npm.jsr.io @jsr/luca__flag

npm ERR! could not determine executable to run

I guess it's because this is missing a bin field: https://npm.jsr.io/@jsr%2fluca__flag

What if jsr always shipped a dummy "bin" script that just imports the main export?

[nakasyou]

@alexgleason I agree with you. Or you can use main field.

[alexgleason]

I created a workaround to this issue, xjsr: https://www.npmjs.com/package/xjsr

npx xjsr @alexgleason/hello

[tom-sherman]

but it does not have a bin field, so npm doesn't know what file to run.

I believe this is the key here and solves this issue as well as being able to run JSR packages inside a package.json script. Right now this is possible with a workaround (see lexicon-community/lpm#12 (comment)) but it's not ideal.