Does Deno block deep imports of modules not whitelisted in the `deno.json` field `exports`?
Question: Does the
The Deno config docs doesn't mention the
https://docs.deno.com/runtime/fundamentals/configuration/
The Intellisense for the field contains "this JSR package" (which seems wrong to assume this is a JSR package, is the field only used by JSR?), and it doesn't explain the full behavior:
https://deno.land/x/deno@v2.1.4/cli/schemas/config-file.v1.json?source=#L583
deno.jsondeno.json field exportsexports cause Deno to block deep import access to any modules not whitelisted in the declared exports, like how Node.js package.jsonpackage.json field exportsexports works?The Deno config docs doesn't mention the
exportsexports field (why?!!):https://docs.deno.com/runtime/fundamentals/configuration/
The Intellisense for the field contains "this JSR package" (which seems wrong to assume this is a JSR package, is the field only used by JSR?), and it doesn't explain the full behavior:
https://deno.land/x/deno@v2.1.4/cli/schemas/config-file.v1.json?source=#L583
Deno
In-depth documentation, guides, and reference materials for building secure, high-performance JavaScript and TypeScript applications with Deno
