Default package.json causes dependency conflict for @salesforce/eslint-config-lwc

[akippiko]

When creating a new Salesforce project with Illuminated Cloud, the generated `package.json` includes incompatible versions of `@salesforce/eslint-config-lwc` and `@lwc/eslint-plugin-lwc`.

Specifically:

- `@salesforce/eslint-config-lwc@^3.2.3` requires `@lwc/eslint-plugin-lwc@^2.0.0`
- However, the generated package.json includes `@lwc/eslint-plugin-lwc@^1.1.2`, leading to npm installation failure due to dependency conflict.

Steps to reproduce:

1. Create a new Salesforce DX project in WebStorm using Illuminated Cloud.
2. Run `npm install`
3. See error: `ERESOLVE unable to resolve dependency tree`

Expected: A compatible set of versions that installs without error.

Suggested fix: Update the default `@lwc/eslint-plugin-lwc` version to `^2.0.0` or higher.

[Scott]

Hi. The default package.json comes from the Salesforce CLI’s template. You should be able to reproduce this behavior by creating a project manually via the CLI in isolation of IC, e.g.:

sf project generate -d <path> -n <name>

Assuming that’s the case, you’ll want to log a bug in the CLI public issue tracker:

https://github.com/forcedotcom/cli/issues

Regards,
Scott Wells

​