Depending on a jsr package in a package published to npm

[fasttime]

We are planning on using a package that is only published to jrs (@std/path) as a dependency in a library that is published to both jsr and npm (@eslint/config-array). Is this use case supported?

My understanding is that npm requires a setting in the npm config file in order to resolve jsr packages (i.e. @jsr:registry=https://npm.jsr.io in .npmrc). But we can't enforce users to put that line in their .npmrc files before they install @eslint/config-array from npm. So, unless a user has already registered jsr in their global or user-specific npm config, the installation would fail if package.json specifies a dependency that cannot be resolved, i.e.:

"@jsr/std__path": "^1.0.2",

I couldn't find any help on how to get around this limitation at https://jsr.io/docs/using-packages, so we thought to ask here in case someone has already faced a similar problem.

[nzakas]

@lucacasonato can you help us out here?