different behavior with npm and pnpm

[sdavids]

Setup

$ mkdir /tmp/test && cd "$_"
$ npm init -y
$ npm i -D @playwright/test@1.53.2 eslint@9.30.1 eslint-plugin-import-x@4.16.1
$ jq '.scripts += {"lint":"eslint ."}' package.json >.tmp && mv .tmp package.json
$ cat <<'EOF' >eslint.config.mjs
import { flatConfigs as importConfigs } from "eslint-plugin-import-x";

export default [importConfigs.recommended];
EOF
$ cat <<'EOF' >playwright.config.mjs
import { defineConfig } from '@playwright/test';

export default defineConfig({});
EOF

npm

Run lint:

$ npm run lint

> test@0.0.1 lint
> eslint .

With npm there will be no error.

pnpm

Get rid of npm stuff and install pnpm stuff …

$ rm -rf node_modules package-lock.json
$ pnpm --silent install

Run lint:

$ pnpm run lint

> [test@0.0.1](mailto:test@0.0.1) lint /private/tmp/test
> eslint .


/private/tmp/test/playwright.config.mjs
  1:10  error  defineConfig not found in '@playwright/test'  import-x/named

✖ 1 problem (1 error, 0 warnings)

 ELIFECYCLE  Command failed with exit code 1.

With pnpm there is an error.

---

https://playwright.dev/docs/test-configuration

I skipped providing a working playwright setup because it would just clutter this PR.

[petercat-assistant]

The issue you're experiencing seems to be related to the different ways npm and pnpm handle package installations and module resolution. The error message indicates that defineConfig is not found in @playwright/test when using pnpm, which suggests a potential issue with how pnpm is resolving the module.

Here are a few steps you can take to troubleshoot and potentially resolve the issue:

1. Check Module Resolution: Ensure that pnpm is correctly resolving the @playwright/test module. You can do this by checking the node_modules directory to see if the module is correctly installed and accessible.

2. Verify pnpm Configuration: Sometimes, pnpm might have different configurations that affect module resolution. Check your pnpm configuration files (like .npmrc or pnpm-workspace.yaml) for any settings that might affect module resolution.

3. Clear pnpm Cache: Try clearing the pnpm cache and reinstalling the packages. You can do this with the following commands:

   pnpm store prune
   pnpm install

4. Check for Known Issues: Look for any known issues related to pnpm and @playwright/test or eslint-plugin-import-x. There might be existing discussions or fixes available.

5. Compare npm and pnpm Installations: Compare the node_modules structure and the installed package versions between npm and pnpm to identify any discrepancies.

If these steps do not resolve the issue, it might be helpful to create a minimal reproducible example and report it to the maintainers of eslint-plugin-import-x or pnpm for further assistance.

If you would like me to search for any known issues or further information, please let me know!

🪧 Tips

For further assistance, please describe your question in the comments and @petercat-assistant to start a conversation with me.