run-p: command not found

[bobalbert-cameronsky]

I know this was asked last year in #67, but I'm running into this issue and there was no solution posted.

npm install does create the node_modules folder, but all the sub folders are empty. Then of course "npm run dev" returns the sh: run-p: command not found error. essentially the same issues as reported in the other discussion.
I've removed the folder several times and done npm install and get the same behavior.

I'm using WPEngine's Local latest Version 9.2.0+6762. as my dev environment on a Mac OS 15.3
Node.js v22.12.0
npm 10.9.0
WP-CLI: WP-CLI 2.11.0
Composer: 2.6.2 2023-09-03
PHP: 8.3.11
MySQL: mysql Ver 8.0.35 for macos13 on x86_64 (MySQL Community Server - GPL)

from PHPStorm:

not sure if my setup is wrong or am I missing something?

Thanks,
Bob

[gregsullivan]

Hi Bob—Thanks for posting this!

I still haven't heard from anyone with definitive details on how they fixed it; just fairly arbitrary things like rebooting (sometimes multiple times), or reinstalling Node.js, etc., and then running npm install again.

I don't use Local, so I don't have any particular insights there.

Some questions for you:

• Are you synching this site to and from a host, or have you only worked on it locally?
• Could you run npm install and paste in the output?
• What is your current Node.js version? (Or npm version.)

[bobalbert-cameronsky]

Greg,

Thanks... i actually got it working and I think i might have to do with permissions maybe. So In Local there is a "tool" that will open your shell for you I believe as the "Local" user. When trying to run npm install it only installed like 12 node modules. see screen shot from previous post.

When I open the same theme folder outside of "Local's" terminal and directly in my terminal as my mac user, it seems to work correctly... installing all the folders needed and npm run dev then works as it finds what it needs.

So there might be something with using the default "local" terminal "user" vs my regular user or how my node is installed. Or could be pathing... not sure.. not a big node user etc... just follow the posted commands. Typcially i just use the terminal in my Local to run wpcli but then even then i usually do it as the mac user.

Thus if others run into this, maybe this is a solution. Not totally sure.'
Bob

[gregsullivan]

Hi Bhrugesh,

Sorry this happened to you as well!

Do you use Local WP for local development?

Could you please try doing the following:

1. Create a file called .npmrc in your project root
2. Add this as the content of the file: omit = null
3. Save and run npm install again, and then try npm run dev

Thanks very much!

[bhrugesh96]

hey @gregsullivan
I fixed it by the way and working fine for me.

Thanks

[gregsullivan]

Perfect, thank you! Did you fix it using the .npmrc file, or did you do something else?

[bhrugesh96]

I added one npm package for run-p globally and it will work fine for me. Yeah I just need to restart my pc after added this package and try again that command and it will work perfectly for me.

[gregsullivan]

Thanks for letting me know—much appreciated!