[import/no-unresolved] when importing from another package in a monorepo

[tpluscode]

Specifically, I have a package with an export map like this

{
  "name": "@hydrofoil/roadshow-ng",
  "exports": {
    ".": "./index.js",
    "./rs-view.js": "./rs-view.js",
    "./viewers.js": "./viewers.js"
  }
}

In other packages I import '@hydrofoil/roadshow-ng/rs-view.js' etc. This gets reported as unresolved.

Interestingly, if I drop the extension or change to .ts, the import plugin no longer complains...

[tpluscode]

Anyone?

[simondean]

Hi. This fixed a similar issue for me. I didn't need to add a exports entry to my package.json files though.

I fixed my issue by adding this to my eslint.cjs file in the root of my monorepo:

    parserOptions: {
        project: ['tsconfig.json', 'packages/*/tsconfig.json'],
        node: true,
    },
    settings: {
        'import/parsers': {
            '@typescript-eslint/parser': ['.ts'],
        },
        'import/resolver': {
            typescript: {
                // See https://github.com/import-js/eslint-import-resolver-typescript for documentation of these settings
                // This `project` entry is needed, in addition to the `project` entry above under `parserOptions`,
                // otherwise eslint-plugin-import's `import/no-unused-modules` rule will not work correctly
                project: ['tsconfig.json', 'packages/*/tsconfig.json'],
            },
        },
    },

[JounQin]

@tpluscode Sorry I'm very late here, can you please provide an online runnable reproduction?

[tpluscode]

@JounQin: https://github.com/tminuscode/resolver-typescript-package-exports

[tpluscode]

Have you had a chance to to look into it @JounQin \

[JounQin]

See #275 and webpack/enhanced-resolve#413