This repository has been archived by the owner on Mar 31, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 70
Can't run $ npm start without error #358
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
FYI, after running npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":">=0.10.0 <7"} (current: {"node":"13.12.0","npm":"6.14.4"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]
npm WARN [email protected] requires a peer of gulp@>=4 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] No repository field.
npm WARN [email protected] No license field.
added 1898 packages from 1601 contributors and audited 21457 packages in 225.95s
51 packages are looking for funding
run `npm fund` for details
found 25 vulnerabilities (8 low, 1 moderate, 15 high, 1 critical)
run `npm audit fix` to fix them, or `npm audit` for details |
@erok415 thank you for letting us know, but we recently deprecated this package in lieu of releasing the new Emulsify - see the README for details. Here are some quick links in case they help:
If you or anyone is interested in maintaining this deprecated package, we are open to making that access possible. But Four Kitchens is pouring all our time/energy into the other now. Thanks again! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
emulsify version (see releases):
[email protected]
node version:
v8.17.0
npm (or yarn) version:
6.13.4
What you did:
After running
$ npm install
, I'm having issues running$ npm start
What happened:
Reproduction repository (if necessary):
Problem description:
I can't run npm install
Suggested solution:
The text was updated successfully, but these errors were encountered: