Add support for import subpath patterns

[rsimp]

🙋 feature request

Add support for import subpath patterns for framework agnostic aliasing

🤔 Expected Behavior

With the following in package.json:

{
  "imports": {
    "#hooks/*": "./src/common/hooks/*",
  }
}

I should be able to import like the following:

import useHook from '#hooks/useHook';

😯 Current Behavior

Parcel already supports glob aliases to achieve the same thing. However import subpath patterns are a standard supported natively in node.

💁 Possible Solution

Implement code in dependency resolution to support imports in package.json. One part of the spec that helps is that imports entries MUST start with # in order to work. If an import starts with '#' then Parcel should check package.json for the imports section before resolving with it's own alias configuration. Webpack uses this same method, or rather it only will resolve '#' imports with package.json.

🔦 Context

While parcel aliasing is useful it's specific to Parcel. Jest, express, other bundlers, typescript all need their own specific configuration to support the same code. Webpack, express, build scripts, and top level jest imports all already support import subpath patterns. Jest mocking is waiting on a third party dependency to get support for mocking apis as well. It would be nice if typescript/vs code supported it as well, but as more packages implement the standard it puts more pressure on other packages to adopt.

Even in its current state I can at least get framework agnostic support for Parcel AND for node.js backend/scripts just like I can with Webpack.

[rsimp]

For more information, webpack achieves this using their enhanced-resolve package. The issue for adding the imports field is: webpack/enhanced-resolve#290

[rsimp]

Really this feature request should be for supporting the entire imports field specification. Not just subpath patterns

[rsimp]

Also esbuild and rollup support import subpath patterns as well

[mischnic]

Will be fixed by #8807 in the next release

[cybergrunge]

Well, it is not. (^2.9.1)

@parcel/core: Failed to resolve '#utils/logger.js' from './src/index.js'

[devongovett]

Please note that exports/imports support is currently opt-in to avoid breaking changes. To enable it, add the following to your project root package.json:

{
  "@parcel/resolver-default": {
    "packageExports": true
  }
}

See the docs for more details: https://parceljs.org/features/dependency-resolution/#package-exports

[cybergrunge]

Thanks, and apologies, I only found this issue when searching for informations about this.