import/no-unresolved does not support multiple nested package.json

Folder / file structure:

.
├── .eslintrc
├── package.json // Package 1
├── src
│   └── package.json // Package 2
│   ├── components
│   │   └── Foo.jsx

Content of Package 2:

{
  "name": "src"
}

This enables me to import Foo.jsx like so (from anywhere):

import Foo from 'src/components/Foo';

This node resolution behaviour is standard as far as I know.

eslint-plugin-import is not able to resolve my files:

  5:23  error  Unable to resolve path to module 'src/components/Foo'  import/no-unresolved

[eightyfive]

Ok thanks.

A better alternative (to my previous solution) is to use Yarn workspaces:

// ./package.json (main)
{
  "private": true,
  "workspaces": ["src"]
}

Note: ./src/package.json remains unchanged, see https://github.com/benmosher/eslint-plugin-import/issues/1272#issue-403798133.

This does not require to install/re-install the local src folder after every change.

And it works with eslint-plugin-import plugin. It does not work. Use relative paths as suggested by @ljharb.

More details here (Stackoverflow).

[eightyfive]

I threw a small Node project on my laptop and @ljharb is right, it does not seem to work outside of node_modules.

The fact that it works when bundling a RN app, must be RN specific then.

I’ll find an alternative, thanks for your help.