You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using jsr: deps via a deno.json file and using "nodeModulesDir": "manual" or (I forget, I think so ?) "nodeModulesDir": "auto" they aren't included in the node_modules dir, which causes issues with Vitest (#23882 (comment)).
When using a package.json with a JSR-enabled .npmrc, deno install works as expected.
I assume you'll want a repro; I need to go hit the hay, so, if so, please ping me so it's at the top of my notifications list tomorrow :)
The text was updated successfully, but these errors were encountered:
This is by design. jsr: specifiers in Deno resolve to remote https urls (ex. jsr:@std/[email protected] resolves to https://jsr.io/@std/path/1.0.8/mod.ts) and so they aren't included in the node_modules directory (they can be included locally in a project by turning on "vendor": true in a deno.json, at which point they'll be in the local vendor folder).
That said, it is possible to use JSR packages with a node_modules directory by installing them through npm by adding the following to an .npmrc file:
Version: Deno 2.x.x (all)
When using
jsr:
deps via adeno.json
file and using"nodeModulesDir": "manual"
or (I forget, I think so ?)"nodeModulesDir": "auto"
they aren't included in the node_modules dir, which causes issues with Vitest (#23882 (comment)).When using a
package.json
with a JSR-enabled.npmrc
,deno install
works as expected.I assume you'll want a repro; I need to go hit the hay, so, if so, please ping me so it's at the top of my notifications list tomorrow :)
The text was updated successfully, but these errors were encountered: