You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The npm run start command fails to execute due to an ESLint configuration issue. The error message indicates that ESLint cannot find the eslint.config.js file and suggests migrating from the old .eslintrc.* configuration to the new eslint.config.js format.
To Reproduce
Steps to reproduce the behavior:
Open a terminal/command prompt.
Navigate to the project directory: C:\Users\rahpatel\source\repos\xperience-by-kentico-lucene\src\Kentico.Xperience.Lucene.Admin\Client.
Run the command: npm run start.
The error message about ESLint's configuration file missing is displayed.
Expected behavior
The npm run start command should run successfully, linting the code and starting the webpack development server without issues.
Screenshots
Library Version
eslint: 9.17.0
npm: 10.8.2
Node.js: 20.18.0
Desktop (please complete the following information):
OS: Windows 11
Browser: Not applicable (command-line issue)
Smartphone (please complete the following information):
Device: Not applicable
OS: Not applicable
Browser: Not applicable
Version: Not applicable
Additional context
ESLint seems to have deprecated support for .eslintignore files, and it requires using the eslint.config.js file instead.
The issue appears to be due to missing or outdated ESLint configuration, specifically the migration from .eslintrc.* to eslint.config.js.
The text was updated successfully, but these errors were encountered:
Hello, the latest version of Kentico.Xperience.Lucene up to date uses eslint version 8.56.0 which does not have this issue. Maybe your local node modules are ahead of the project ?
From what I see it seems that you are not running npm i command to install the dependencies locally and therefore you are using global dependencies. Try to install local dependencies and repeat the process.
The project has ESLint 8.56.0 as it's dependency and since ESLint 9+ introduced new format of configuration files it is not compatible.
Describe the bug
The npm run start command fails to execute due to an ESLint configuration issue. The error message indicates that ESLint cannot find the eslint.config.js file and suggests migrating from the old .eslintrc.* configuration to the new eslint.config.js format.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The npm run start command should run successfully, linting the code and starting the webpack development server without issues.
Screenshots
Library Version
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: