The proposal currently lists a secondary imports field. This hasn't been implemented anywhere afaik. We should decide what the solution for that use case is.

Support Status

General Support

• node
• bun (some gotchas, see Implement package.json "#imports" field support from fork() oven-sh/bun#16017)
• deno (fix: support package.json imports in a Deno workspace denoland/deno#30198)
• oxc_resolver
• typescript: https://www.typescriptlang.org/docs/handbook/modules/reference.html#packagejson-imports-and-self-name-imports
• enhanced-resolve
• @rollup/plugin-node-resolve (feat(node-resolve): support pkg imports and export array rollup/plugins#693)
• resolve.exports (https://github.com/lukeed/resolve.exports)
• vite (https://github.com/vitejs/vite/tree/2f9428d1ffd988e30cb253d5bb84844fb1654e86/playground/resolve/imports-path)
• esbuild
• resolve (Node.js imports field is not supported browserify/resolve#327); affects:
  • postcss-import (Subpath imports postcss/postcss-import#573)

#/ Allowed

• node (module: allow subpath imports that start with #/ nodejs/node#60864, pending release)
• bun (module: allow subpath imports that start with #/ oven-sh/bun#25476)
• deno (feat(node): allow subpath imports that start with '#/' denoland/deno#31520, pending release)
• oxc_resolver (feat: allow subpath imports that start with #/ oxc-project/oxc-resolver#907, pending chore: release v11.16.0 oxc-project/oxc-resolver#906)
• typescript (Port TypeScript PR #62844: Gate #/ subpath imports on NodeNext and Bundler microsoft/typescript-go#2330, Allow subpath imports that start with #/ microsoft/TypeScript#62844, v6.0.0)
• enhanced-resolve v5.18.4
• @rollup/plugin-node-resolve
• resolve.exports
• vite (already worked but regression test added in test: add regression test for #/ in subpath imports vitejs/vite#21265)
• esbuild (fix: allow subpath imports that start with #/ evanw/esbuild#4361)
• resolve; affects:
  • postcss-import (Subpath imports postcss/postcss-import#573)