This discrepancy is likely because the package-lock.json or previously cached modules contain versions that conflict with your intended updates or installations.

Why is this happening?

1. Cached Node Modules:

   • npm install uses the existing node_modules and package-lock.json.
   • If there are version conflicts between dependencies in package-lock.json and your local environment, errors occur.

2. Project Initialization Differences:

   • npm init playwright@latest sets up a fresh project environment every time, automatically fetching and resolving the correct dependencies.
   • This means it ignores the previous cache or package-lock.json, ensuring a clean installation.

3. Node Version Incompatibility:

   • Playwright and many packages have dependencies that work best with specific Node.js versions.
   • Your npm init playwright@latest even warns about the Node version incompatibility but still manages to work because it creates a fresh environment.

Solution

1. Clear Cache

First, clear the npm cache to ensure no remnants of old installations remain.

npm cache clean --force

2. Delete Old Files

Remove the node_modules folder and package-lock.json to get a clean slate.

rm -rf node_modules package-lock.json

If you're on Windows (PowerShell):

rm -r node_modules
rm package-lock.json

3. Reinstall Dependencies

Run npm install to reinstall the dependencies fresh.

npm install

4. Update Rollup (If Applicable)

If Rollup version issues persist, manually install the correct version:

npm install rollup@latest --save-dev

Or, if you need a specific version:

npm install [email protected] --save-dev

5. Verify Node Version Compatibility

Check your Node version and upgrade it if necessary.

node -v
npm -v

If you find the Node version is outdated, upgrade it using NVM:

nvm install 20  # Or whichever version you'd prefer
nvm use 20

Then, reinstall npm:

npm install -g npm

6. Clean Project Installation (Recommended)

As a last resort, recreate the project setup:

npm init playwright@latest -- --ct