TypeError: npm.commands.start.apply is not a function at /usr/local/lib/node_modules/foundation-cli/lib/commands/watch.js:26:24

[xMaedayx]

What should happen?

I am using macOS Ventura 13.2.1 (using VSC as my code editor)
I downloaded the Foundation-Sites-CSS file and also ran the command line

npm install foundation-sites

Running foundation new for the first time, and I'm assuming it should just create a directory with all of the basic files.

What happens instead?

I installed node.js along with yarn after receiving my first error

'There were some problems during the installation.

✓ New project folder created.
✗ Node modules not installed. Try running yarn install manually.

Once you've resolved the above issues, run foundation watch while inside the HumanKitten folder.`

Now when I run

foundation watch

I get this error...

`/usr/local/lib/node_modules/foundation-cli/lib/commands/watch.js:26
npm.commands.start.apply(this, []);
^

TypeError: npm.commands.start.apply is not a function
at /usr/local/lib/node_modules/foundation-cli/lib/commands/watch.js:26:24

Node.js v18.15.0`

Possible Solution

Perhaps I have to create an empty directory and open it with VSC and do

npm init

...

Test Case and/or Steps to Reproduce (for bugs)

how to reproduce:
1.) npm install --global function
2.) foundation new
3.) npm install
4.) npm install -g yarn
5.) yarn install
6.) foundation watch

Context

I would like to understand how the foundation Command line application is suppose to run normally and why I am receiving an error about the javascript file within the foundation-cli.
...

Your Environment

• Foundation version(s) used: 6.7.5
• Browser(s) name and version(s): N/A
• Device, Operating System and version: MacOS air m1
• Link to your project: N/A

Checklist

• [ x] I have read and follow the CONTRIBUTING.md document.
• [x ] There are no other issues similar to this one.
• [ x] The issue title and template are correctly filled.