@mst We just released Local 9.2.6 yesterday with a change that may fix this for you if you’re using npm in Local’s site shell with mostly dev dependencies:
- Site shells no longer inherit NODE_ENV=production from Local. npm commands you run in site shells now use the default NODE_ENV value (development). You can still override this in your shell config if needed.
Please could you try upgrading to Local 9.2.6 if you haven’t yet to see if that solves your issue?
You can find the latest version at https://localwp.com/releases/ or choose Local → Check for updates.
After upgrading, be sure to reopen any terminals or editors/IDEs launched from Local’s site shell before re-testing with npm install.