framework cli - node modules won't install

[JHunnicutt]

What should happen?

When I run foundation new --framework emails it should install the dependencies.

What happens instead?

I get the error that "node modules are not installed" and to try installing node manually.

MacBook-Pro:Email-Project Jordan$ foundation new --framework emails
? What's the project called? (no spaces) hg-emails

          _____
         /     \
        /=   . |
    ___| ==  | /    Thanks for using ZURB Foundation for Emails!
   /   | ===  \     -------------------------------------------
   |   | ====  |    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...

npm ERR! git rev-list -n1 4.0: fatal: ambiguous argument '4.0': unknown revision or path not in the working tree.
npm ERR! git rev-list -n1 4.0: Use '--' to separate paths from revisions, like this:
npm ERR! git rev-list -n1 4.0: 'git <command> [<revision>...] -- [<file>...]'
npm ERR! git rev-list -n1 4.0:

There were some problems during the installation.

 ✓ New project folder created.
 ✗ Node modules not installed. Try running npm install manually.
 ✓ Bower components installed.

Once you've resolved the above issues, run foundation watch while inside the hg-emails folder.

I see that my project partially installed from the folder structure below.

When I run npm install in any place within my project folder, errors are returned.

MacBook-Pro:hg-emails Jordan$ npm install
npm WARN deprecated [email protected]: 🙌  Thanks for using Babel: we recommend using babel-preset-env now: please read https://babeljs.io/env to update!
npm WARN deprecated [email protected]: Use UnCSS through gulp-postcss instead.
npm WARN deprecated [email protected]: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated [email protected]: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated [email protected]: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/
npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated [email protected]: the module is now available as 'css-select'
npm WARN deprecated [email protected]: Use uuid module instead
npm WARN deprecated [email protected]: This package is discontinued. Use lodash@^4.0.0.
npm WARN deprecated [email protected]: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated [email protected]: This project is unmaintained
npm WARN deprecated [email protected]: I wrote this module a very long time ago; you should use something else.
npm WARN deprecated [email protected]: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated [email protected]: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
npm WARN deprecated [email protected]: the module is now available as 'css-what'
npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated [email protected]: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated [email protected]: This project is unmaintained
npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated [email protected]: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm ERR! code 1
npm ERR! Command failed: git checkout 4.0
npm ERR! error: pathspec '4.0' did not match any file(s) known to git.
npm ERR!

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/admin/.npm/_logs/2019-06-11T10_17_07_683Z-debug.log

Possible Solution

I see from other errors experienced, that the Node version might have something to do with it. I'm on Node 10.14.1.

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

How to reproduce:

1. Have Foundation cli installed or install it by running npm install --global foundation-cli
2. Run foundation new --framework emails. It will be unsuccessful.
3. Run npm install from your project folder. It will also be unsuccessful.

Context

I have been tasked with redesigning my companies email templates. I recently learned about Zurb's template stack and want very much to use it with this project, as it will speed up production time for what I'm having to do.

Your Environment

• Foundation version(s) used: 2.2.5
• Node version used: 10.14.1
• Browser(s) name and version(s): Chrome 74.0.3729.169
• Device, Operating System and version: MacBook Pro 2014 15", MacOS 10.13.6
• Link to your project:

Checklist

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

[DanielRuf]

Hi @JHunnicutt,

This is due to the gulpjs team which has deleted the tag that we and others use.

I'm closing this as duplicate of foundation/foundation-cli#109

Please file issues related to the CLI at https://github.com/zurb/foundation-cli/issues/

[DanielRuf]

You can change the line in your package.json to read "gulp": "^4.0.0".