Help Starting Over

[maltmaster]

I am returning to Foundation after an abscence of about 2 two years. My last project was with Version 6.3. A lot has changed with the packages used for installationit seems. I am on the latest release of Win 10 Pro Version 21H2 OS build 19044.1706. I used Powershell in administrator mode.
I researched the messages on the Web, Most suggestions were several years old and led to yet more errors.

I hope someone can help me out. Thanks for your attention.

Here is the log of my latest attempt to install.
++++++++++++++++++++++++++++++++++++++++++++++

PS K:\0newfoundation> git --version
git version 2.35.1.windows.2
PS K:\0newfoundation> node -v
v14.19.2
PS K:\0newfoundation> npm -v
8.10.0
PS K:\0newfoundation> npm install -g foundation-cli

changed 192 packages, and audited 435 packages in 1m

34 packages are looking for funding
run npm fund for details

3 vulnerabilities (2 moderate, 1 high)

To address all issues, run:
npm audit fix

Run npm audit for details.
PS K:\0newfoundation> npm audit
found 0 vulnerabilities
PS K:\0newfoundation> npm audit fix

up to date, audited 1 package in 658ms

found 0 vulnerabilities

PS K:\0newfoundation> foundation new
? What are you building today? A website (Foundation for Sites)
? What's the project called? (no spaces) test-it
? Which template would you like to use? Panini Template: includes Handlebars templates and Sass/JS compilers

        .
       /|     ,
  , /|/  \/| /|       Thanks for using Foundation for Sites!
 /|/       |/ |       -------------------------------------------

|| || Let's set up a new project.
_| ^^ ^^ |/ It shouldn't take more than a minute.
| -[O]--[O]- |
| , |
| ... |
______/

Downloading the project template...
Done downloading!

Installing dependencies...

undefined

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 test-it folder.

[guci0]

Forgot about "foundation new" use "npm start". And use "nvm use 14" // node 14

[jameswilson]

Forget about "foundation new" use "npm start".

There must be a step before npm start to obtain the correct base install for a foundation site.

Docs (https://get.foundation/sites/docs/installation.html) state: yarn add foundation-sites

which creates a fairly empty package.json and npm start doesnt work.

What is the proper process to get started anew?

[jameswilson]

Nevermind, I wrote up a separate answer with what I found that works (using foundation new).

[jameswilson]

What I found that finally works:

Ensure nvm is installed and available on path.
Ensure python2 is installed and available on path.
(On Mac) Ensure ComandLineTools for XCode is installed, so you can compile node-sass via node-gyp:

nvm install 14  # because foundation doesn't work with node 16 yet.
nvm use 14
npm install --global foundation-cli
foundation new --framework sites --template panini --directory my-project
# Or (basic templates instead of panini)
foundation new --framework sites --template basic --directory my-project
cd my-project
nvm use 14  # because it switches back to whatever your default is when you cd (in my case node 16).
node -v > .nvmrc  # ensure node 14 is used when you cd into the project in the future.
yarn install -std=c++14  # on recent MacOS GCC has problems compiling node-sass, ymmv.
yarn start  # or npm start

The foundation site should be launched on your local system, available in a web browser at http://localhost:8000

[maltmaster]

Thanks to guci0 for his help and to jameswilson for expanding on that answer. Running under NVM control works.

One further question: Is Python 2 really still necessary? I believe I saw somewhere in the Node docs that Python 3.?? was enough.