v6.7.4 Installation Instructions - The best way now is?

[ITZAP]

Windows 10 PC Running:
npm v8.1.3
node.js v14.18.1
git windows v2.33.1
yarn v1.22.17
foundation-cli v2.3.0

In the past I have always used the "foundation-cli" v2.2.6 installation routine, which worked nicely.
But now that has been updated to v2.3.0, the commands "foundation build" and "foundation watch" are dead ducks.

So instead, I followed the "Foundation for Sites Template" README.MD with these results:

=============
### Using the CLI

cd todesiredfolder
foundation new --framework sites --template basic
foundation_v6-7-4 (the foldername I entered)

Results In:
There were some problems during the installation.
New project folder created.
Node modules not installed. Try running yarn install manually.

cd foundation_v6-7-4
yarn install

Results In:
node_modules folder is created.
==> This now CONTAINS 506 FOLDERS !! Not just the dependencies listed in package.json.
QUESTIONS: Why? Surely all those are not required? What have I done wrong?

yarn start

Results In:
Runs gulpfile.js, generates css\app.css, opens Browsersnc window, acts the same as "foundation watch". Ctrl+C to end.
ALL GOOD !

==============
### Manual Setup

cd todesiredfolder
git clone https://github.com/zurb/foundation-sites-template foundation_v6-7-4

Results In:
New project folder created.
Node modules not installed.

cd foundation_v6-7-4
npm install

Results in (after 1 minute wait):
node_modules folder is created. CONTAINS 506 FOLDERS !!

and all this

npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.

added 716 packages, and audited 717 packages in 1m

22 packages are looking for funding
  run `npm fund` for details

35 vulnerabilities (7 moderate, 28 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

===========

npm start

Results In:
Runs gulpfile.js, generates css\app.css, opens Browsersnc window, acts the same as "foundation watch". Ctrl+C to end.
ALL GOOD !

============
CONCLUSION:
(1) For me, the first method "Using the CLI" was easier and quicker.
(2) I do not understand why 506 dependencies are installed in the "node_modules" folder ? Advice much appreciated.

[joeworkman]

I do not understand why 506 dependencies are installed in the "node_modules" folder ? Advice much appreciated.

Welcome to "modern" web development! LOL

I agree that it's pretty ridiculous. dependency management has become pretty insane with the JS community. I plan on addressing this in Foundation 7 by moving away from JS for most of the development dependencies.

[maietta]

In the past, I have created a docker image for foundation but I no longer have the files. It is trivial to do but the advantage is having everything ready-to-go using docker. Maintenance is much easier this way. It seems to me that this ought to be the official direction for Foundation and similarly situated libraries with so many dependencies.

[joeworkman]

I have not seen any other open source frameworks supply docker images. Do you know of any? I am aware of what docker is but I have personally never used it.

[maietta]

Generally speaking, I have not seen the use of Docker for CSS/JS front-end tools but repeatedly found myself thinking that many of the struggles people keep having with installation and upgrades could be mitigated with the use of Docker. Since Docker is available on every operating system that most every Framework is available for, it seems to be a logical path to knock out a majority of people's problems I keep seeing in the issues section.

[ITZAP]

WARNING to those who installed foundation v6.7.4 following either of the 2 methods described above.
DO NOT attempt to fix deprecated dependencies in the "node_modules" folder by running the command:
npm audit fix --force

Because that updates gulp-sass to v5.0.0,
Then when you enter:
npm start
You will get:
ReferenceError: primordials is not defined

Your installation will be broken.

[joeworkman]

The force command basically breaks all dependency checks. Therefore, it's definitely not recommended to do that.