14.1.1 raises import/no-unresolved in eslint.

[jovanmaric]

A bug is a crash or incorrect behavior. If you have a debugging or troubleshooting question, please open a discussion.

Environment

1. Ruby version: /
2. Rails version: /
3. Shakapacker/Webpacker version: /
4. React on Rails version: 14.1.1

Behavior

Eslint raises Unable to resolve path to module 'react-on-rails' import/no-unresolved on version 14.1.1, but not on version 14.1.0.

Small, reproducible repo

// package.json
{
  "type": "module",
  "dependencies": {
    "eslint": "^9.18.0",
    "eslint-plugin-import": "^2.31.0",
    "react-on-rails": "14.1.1"
  }
}

// eslint.config.js
import importPlugin from 'eslint-plugin-import';
import js from '@eslint/js';

export default [
  js.configs.recommended,
  importPlugin.flatConfigs.recommended,
  {
    files: ['**/*.{js,mjs,cjs}'],
    languageOptions: {
      ecmaVersion: 'latest',
      sourceType: 'module',
    },
    rules: {
      'no-unused-vars': 'off',
      'import/no-dynamic-require': 'warn',
      'import/no-nodejs-modules': 'warn',
    },
  },
];

// test.js
import ReactOnRails from 'react-on-rails';

Run with:
eslint test.js

[justin808]

Thanks! Investigating!

[justin808]

@jovanmaric is this only an eslint issue?

[Judahmeek]

It likely is.

The issue is: eslint-plugin-import currently does not support subpaths

I'm not absolutely sure why we didn't encounter this issue when updating ReactOnRails Pro, but it's possible that either the node or typescript import resolvers do support subpaths.

Either that or our eslint configuration just doesn't catch undefined imports.

Anyway, I'm going to take the code from here & find a solution, starting with re-adding the main rule back.

[jovanmaric]

@jovanmaric is this only an eslint issue?

Thanks all for the quick responses. Yes it is only an eslint issue. React on rails works perfectly.