New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] npm install doesn't work #20
Comments
ping. i have same issue on this hope team support/dev can solved on this. Thanks |
Same here on ubuntu |
I just purchased the pro company version and have the exact same issue on windows. Any hint on how to solve that fast without having to search a lot ? |
I was able to bypass that error in 2 steps.
the node modules are then properly charged with npm install command and you can then use the gulp command to build too hope it helps while waiting for support to upload there code or dependencies |
Try this, tested with node v18.12.1 & npm v8.19.2:
|
@azri-cs Thank you so much bro.. this works.. :D :D |
@azri-cs thank you for that. If anyone has any issues with gulp.series() not function make sure that gulp is using 4.0.0+ in the package.json and then also fix the gulp-autoprefixer. If anyone wishes to get the corrected files I am happy to email them over. |
Does anyone know how to get the gulp build:dev command to work? |
see #18 |
Version
1.1.1
Reproduction link
https://github.com/creativetimofficial/ct-impact-design-system-pro
Operating System
macOS Monterey 12.5
Device
Macbook Pro
Browser & Version
Chrome latest
Steps to reproduce
Download the pro package
unzip and cd to the directory
install gulp with npm install gulp-cli
npm install
What is expected?
It should build the website locally
What is actually happening?
npm install
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 resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
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 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. (debug-js/debug#797)
npm WARN deprecated request@2.88.2: request has been deprecated, see request/request#3142
npm WARN deprecated axios@0.19.0: Critical security vulnerability fixed in v0.21.1. For more information, see axios/axios#3410
npm WARN deprecated popper.js@1.16.0: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
npm ERR! code E401
npm ERR! Incorrect or missing password.
npm ERR! If you were trying to login, change your password, create an
npm ERR! authentication token or enable two-factor authentication then
npm ERR! that means you likely typed your password in incorrectly.
npm ERR! Please try again, or recover your password at:
npm ERR! https://www.npmjs.com/forgot
npm ERR!
npm ERR! If you were doing some other operation then your saved credentials are
npm ERR! probably out of date. To correct this please try logging in again with:
npm ERR! npm login
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/kalaisel/.npm/_logs/2022-08-11T17_26_32_199Z-debug-0.log
Solution
Additional comments
The text was updated successfully, but these errors were encountered: