install webpack using npm gives max call stack exceeded errror - npm

npm i -D webpack
gives me the
npm ERR! Maximum call stack size exceeded
do i need to run the below command to install webpack
npm install --no-optional webpack --save-dev
why i am not able to install webpack with npm i webpack ?
i am using below versions
node - 8.11.1
npm -5.6.0
package.json
"dependencies": {
"react": "^16.5.2",
"react-dom": "^16.5.2"
},
"devDependencies": {
"babel": "^6.23.0",
"babel-core": "^6.26.3",
"babel-loader": "^8.0.4",
"babel-preset-env": "^1.7.0",
"babel-preset-react": "^6.24.1",
"html-webpack-plugin": "^3.2.0",
"http-server": "^0.11.1",
"webpack-cli": "^3.1.2",
"webpack-dev-server": "^3.1.9"
}

I would recommend the installation process as described on the webpack website
npm install --save-dev webpack
Or if you want a specific version
npm install --save-dev webpack#<version>
Note: If your using webpack v4 or later you also need to install the CLI
npm install --save-dev webpack-cli
If --save-dev argument doesn't work try deleting package-lock.json and retry
If you're still experiencing problems, here's a link to a GitHub issue with more solutions

Related

Version mismatch vite and quasar

Trying to install Quasar on my Vite (Vue 3) project. Getting the following error:
$ npm install -D #quasar/vite-plugin#latest sass#1.32.12
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: diop-dash#0.0.0
npm ERR! Found: #vitejs/plugin-vue#4.0.0
npm ERR! node_modules/#vitejs/plugin-vue
npm ERR! dev #vitejs/plugin-vue#"^4.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer #vitejs/plugin-vue#"^2.0.0 || ^3.0.0" from #quasar/vite-plugin#1.2.3
npm ERR! node_modules/#quasar/vite-plugin
npm ERR! dev #quasar/vite-plugin#"1.2.3" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
From this it looks like quasar's vite plugin is looking for the 2.0.0 or 3.0.0 version of #vitejs/plugin-vue but I have 4.0 installed. Is quasar not compatible with the new one, will I run into trouble if I use the --force flag? Is there another way to resolve this that doesn't involve downgrading my Vite setup?
From package.json
"dependencies": {
"#quasar/extras": "^1.15.8",
"pinia": "^2.0.28",
"quasar": "^2.10.2",
"vue": "^3.2.45",
"vue-router": "^4.1.6"
},
"devDependencies": {
"#quasar/vite-plugin": "^1.2.3",
"#rushstack/eslint-patch": "^1.1.4",
"#types/node": "^18.11.12",
"#vitejs/plugin-vue": "^4.0.0",
"#vue/eslint-config-prettier": "^7.0.0",
"#vue/eslint-config-typescript": "^11.0.0",
"#vue/tsconfig": "^0.1.3",
"eslint": "^8.22.0",
"eslint-plugin-vue": "^9.3.0",
"npm-run-all": "^4.1.5",
"prettier": "^2.7.1",
"sass": "^1.32.12",
"typescript": "~4.7.4",
"vite": "^4.0.0",
"vue-tsc": "^1.0.12"
}

vuejs 3 I deleted folder node_modules and now npm install has error

I have a work project, but I deleted folder node_modules and now npm install has error.
node v16.13.2
#vue/cli 4.5.15
my package.json
"dependencies": {
"#capacitor/android": "3.4.3",
"#capacitor/app": "1.1.0",
"#capacitor/core": "3.4.1",
"#capacitor/haptics": "1.1.4",
"#capacitor/keyboard": "1.2.2",
"#capacitor/status-bar": "1.0.8",
"#ionic/vue": "^6.0.9",
"#ionic/vue-router": "^6.0.0",
"#popperjs/core": "^2.11.2",
"axios": "^0.25.0",
"core-js": "^3.6.5",
"eslint-loader": "^4.0.2",
"vue": "^3.2.21",
"vue-axios": "^3.4.0",
"vue-router": "^4.0.12",
"vuex": "^4.0.2"
},
"devDependencies": {
"#babel/eslint-parser": "^7.17.0",
"#babel/eslint-plugin": "^7.16.5",
"#capacitor/cli": "3.4.1",
"#vue/cli-plugin-babel": "~4.5.15",
"#vue/cli-plugin-eslint": "~4.5.15",
"#vue/cli-service": "~4.5.15",
"#vue/compiler-sfc": "^3.0.0",
"eslint": "^7.0.0",
"eslint-plugin-vue": "^7.0.0"
},
npm install
# npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: dev.infi.loc#0.1.0
npm ERR! Found: eslint#7.32.0
npm ERR! node_modules/eslint
npm ERR! dev eslint#"^7.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer eslint#">= 1.6.0 < 7.0.0" from #vue/cli-plugin-eslint#4.5.17
npm ERR! node_modules/#vue/cli-plugin-eslint
npm ERR! dev #vue/cli-plugin-eslint#"~4.5.15" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\xxx\AppData\Local\npm-cache\eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\xxx\AppData\Local\npm-cache\_logs\2022-03-27T14_01_53_031Z-debug.log
How can I fix it? Please help. Thanks in advance.
Error screen https://i.stack.imgur.com/QmLtI.png
It happened to me a while ago, i dont know if the solutions is still going to work but, tried deleting the package.json then use npm init hen run dependency-check in your project directory followed by a npm install
A solution that worked for me was upgrading #vue/cli-plugin-eslint to ^5.0.4 (The ^ means "up to next major").
On a side note, you should keep all your packages as up-to-date as possible for security reasons.

Can't upgrade React-Native project due dependencies

I am trying to update my RN project from 0.62.2 to the latest one (currently 0.63.3).
I am just running npm update and get errors:
npm ERR! Found: react#17.0.1
npm ERR! node_modules/react
npm ERR! react#"^17.0.1" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react#"16.13.1" from react-native#0.63.3
npm ERR! node_modules/react-native
npm ERR! react-native#"^0.63.3" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
Before running npm update I had ran npx npm-check-updates -u and got the following:
#react-native-community/netinfo ^5.9.5 → ^5.9.9
#react-navigation/drawer ^5.8.6 → ^5.11.4
#react-navigation/native ^5.7.1 → ^5.8.10
#react-navigation/stack ^5.7.1 → ^5.12.8
#types/react ^16.9.43 → ^17.0.0
amazon-cognito-identity-js ^3.3.3 → ^4.5.5
aws-amplify ^3.0.21 → ^3.3.10
axios ^0.19.2 → ^0.21.0
graphql ^0.11.7 → ^15.4.0
graphql-tag ^2.10.4 → ^2.11.0
moment-timezone ^0.5.31 → ^0.5.32
react ^16.11.0 → ^17.0.1
react-native ^0.62.2 → ^0.63.3
react-native-base64 0.0.2 → 0.1.0
react-native-gesture-handler ~1.5.0 → ~1.9.0
react-native-reanimated ~1.4.0 → ~1.13.2
react-native-safe-area-context ^0.7.3 → ^3.1.9
react-native-screens 2.0.0-alpha.12 → 2.15.0
react-native-simple-crypto ^0.2.13 → ^0.2.15
react-native-vector-icons ^6.7.0 → ^7.1.0
react-navigation ^4.4.0 → ^4.4.3
#babel/core 7.8.7 → 7.12.9
#babel/runtime 7.8.7 → 7.12.5
babel-jest 24.9.0 → 26.6.3
metro-react-native-babel-preset 0.56.4 → 0.64.0
react-test-renderer 16.9.0 → 17.0.1
OK, I summarise from the error that react#^17.0.1 is wrong for react-native#0.63.3 which requires react#16.13.1 but this was produced by npx npm-check-updates -u - why it makes incompatible deps tree?..
If I change manually react version to "^16.0.0", npm install fails with:
npm ERR! Found: react#16.14.0
npm ERR! node_modules/react
npm ERR! react#"^16.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react#"16.13.1" from react-native#0.63.3
npm ERR! node_modules/react-native
npm ERR! react-native#"^0.63.3" from the root project
Why "react#16.14.0"?! From where?
I just can't understand how all this s..tuff works.. Please, suggest.
My current package.json:
{
"name": "Proj",
"version": "0.0.1",
"private": true,
"scripts": {
"android": "react-native run-android",
"ios": "react-native run-ios",
"start": "react-native start",
"test": "jest"
},
"dependencies": {
"#react-native-community/masked-view": "^0.1.10",
"#react-native-community/netinfo": "^5.9.9",
"#react-navigation/drawer": "^5.11.4",
"#react-navigation/native": "^5.8.10",
"#react-navigation/stack": "^5.12.8",
"#types/react": "^17.0.0",
"amazon-cognito-identity-js": "^4.5.5",
"aws-amplify": "^3.3.10",
"axios": "^0.21.0",
"graphql": "^15.4.0",
"graphql-tag": "^2.11.0",
"i18n-js": "^3.8.0",
"moment-timezone": "^0.5.32",
"react": "^16.0.0",
"react-native": "^0.63.3",
"react-native-avatar-social": "0.0.3",
"react-native-base64": "0.1.0",
"react-native-gesture-handler": "~1.9.0",
"react-native-linear-gradient": "^2.5.6",
"react-native-localize": "^2.0.1",
"react-native-reanimated": "~1.13.2",
"react-native-safe-area-context": "^3.1.9",
"react-native-screens": "2.15.0",
"react-native-simple-crypto": "^0.2.15",
"react-native-tab-view": "^2.15.2",
"react-native-tab-view-viewpager-adapter": "^1.1.0",
"react-native-uuid-generator": "^6.1.1",
"react-native-vector-icons": "^7.1.0",
"react-native-video": "^4.4.5",
"react-native-viewpager": "^0.2.13",
"react-native-zeroconf": "github:atlascoder/react-native-zeroconf",
"react-navigation": "^4.4.3",
"rn-fetch-blob": "^0.12.0"
},
"devDependencies": {
"#babel/core": "7.12.9",
"#babel/runtime": "7.12.5",
"babel-jest": "26.6.3",
"metro-react-native-babel-preset": "0.64.0",
"react-test-renderer": "17.0.1"
},
"rnpm": {
"assets": [
"./assets/fonts/"
]
}
}
UPDATE
Following #anthony-marino suggestion I made manual dependencies update by update helper, and the I returned to the issue that moved my to upgrade!!
npm ERR! Found: react#16.13.1
npm ERR! node_modules/react
npm ERR! react#"16.13.1" from the root project
npm ERR! peer react#"^16.0" from #react-native-community/viewpager#4.2.1
npm ERR! node_modules/#react-native-community/viewpager
npm ERR! peer #react-native-community/viewpager#"*" from react-native-tab-view-viewpager-adapter#1.1.0
npm ERR! node_modules/react-native-tab-view-viewpager-adapter
npm ERR! react-native-tab-view-viewpager-adapter#"^1.1.0" from the root project
npm ERR! 15 more (#react-navigation/core, #react-navigation/drawer, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react#"16.11.0" from react-native-zeroconf#0.12.3
npm ERR! node_modules/react-native-zeroconf
npm ERR! react-native-zeroconf#"github:atlascoder/react-native-zeroconf" from the root project
npm ERR!
And the thing that runs me out..
I have a component from #react-native-community/viewpager and why if it requires peerDep react#"^16.0" - why it doesn't accept react#16.13.1. The ^16.0 means all fresher that 16.*, doesn't it?! When I check ^16.0 on npm semver calculator - it shows me 16.13.1 as suitable..
WORKAROUND
On trapping to this trouble while update:
Delete node_modules and package-lock.json
npm i
When npm i fails - remove failing dependencies
After completion of npm i - manually install removed dependencies
From your logs: react-native 0.63.3 needs react#"16.13.1", but found react#"^17.0.1". Just downgrade your react via npm install react#16.13.1 and try npm install again. It should work without errors. If you run npm outdated you'll see that "react" is outdated. But it's unlikely that you're going to have all your packages in the latest version.
so I've also run into this problem when I migrated from RN 0.63.1 to 0.64.1 so I solved it in this way:
Step run npx react-native upgrade for me it updated react and react-native
Then I've updated these dependencies mannually:
"#babel/core": "^7.12.9",
"#babel/runtime": "^7.12.5",
"#react-native-community/eslint-config": "^2.0.0",
"babel-jest": "^26.6.3",
"eslint": "7.14.0",
"jest": "^26.6.3",
"metro-react-native-babel-preset": "^0.64.0",
"react-test-renderer": "17.0.1"
you could use this tool to see what changes did these command npx react-native upgrade and what changes you have to do it manualy
https://react-native-community.github.io/upgrade-helper/?from=0.63.1&to=0.64.1
Then run npm install --force to update package-lock.json with new dependency that you've added manually.
If you have tests with Jest probably then you have to adjust a few things as well go to jest.configs.js and make sure you have here react-native and #react-native as well
transformIgnorePatterns: [
'node_modules/(?!(jest-)?react-native|#react-native|#react-native-community)',
],
and probably you'll have some problem with these mock as well
// The old way
jest.mock('react-native/Libraries/Animated/src/NativeAnimatedHelper');
// Here path was updated
jest.mock('react-native/Libraries/Animated/NativeAnimatedHelper');
Now you should be good to go, this example was for upgrading RN from 0.63.1 to 0.64.1 but it could work for you as well.
p.s I'm using node -v 14.15.4 and npm -v 7.7.6 you may have less problem if you're using npm v6
This solved my problem.
npm install #react-native-community/masked-view --force
I had to use :
npm i --legacy-peer-deps

MEVN app deployment to Heroku failed because of 'vue-cli-service' not found

So, I tried to deploy my MEVN application to Heroku by following Traversy's tutorial (https://www.youtube.com/watch?v=71wSzpLyW9k). I followed all the steps that he outlined in the tutorial. His tutorial is for the MERN stack, but it's very similar apart from the front-end framework, so I figured it would work for my MEVN app too.
The main parts of the tutorial were adding this snippet to my app.js:
if(process.env.NODE_ENV === 'production') {
//Set static folder
app.use(express.static('client/build'));
app.get('*', (req, res) => {
res.sendFile(path.resolve(__dirname, 'client', 'build', 'index.html'));
});
}
and this script in package.json:
"heroku-postbuild": "NPM_CONFIG_PRODUCTION=false npm install --prefix client && npm run build --prefix client"
The "heroku-postbuild" script ran when I did "git push heroku master", so it seemed like the deployment was going to work until it got to the point of trying to build the client side.
The details of the build log are below:
-----> Node.js app detected
-----> Creating runtime environment
NPM_CONFIG_LOGLEVEL=error
NODE_ENV=production
NODE_MODULES_CACHE=true
NODE_VERBOSE=false
-----> Installing binaries
engines.node (package.json): unspecified
engines.npm (package.json): unspecified (use default)
Resolving node version 12.x...
Downloading and installing node 12.18.2...
Using default npm version: 6.14.5
-----> Installing dependencies
Installing node modules
> puppeteer#3.0.1 install /tmp/build_44931d5da2ada9ea8e2cd227fa7e5a8a/node_modules/puppeteer
> node install.js
> nodemailer#6.4.6 postinstall /tmp/build_44931d5da2ada9ea8e2cd227fa7e5a8a/node_modules/nodemailer
> node -e "try{require('./postinstall')}catch(e){}"
=== Nodemailer 6.4.6 ===
Thank you for using Nodemailer for your email sending needs! While Nodemailer
itself is mostly meant to be a SMTP client there are other related projects in
the Nodemailer project as well.
For example:
> IMAP API ( https://imapapi.com ) is a server application to easily access
IMAP accounts via REST API
> NodemailerApp ( https://nodemailer.com/app/ ) is a cross platform GUI app to
debug emails
> node-cron#2.0.3 postinstall /tmp/build_44931d5da2ada9ea8e2cd227fa7e5a8a/node_modules/node-cron
> opencollective-postinstall
> bcrypt#4.0.1 install /tmp/build_44931d5da2ada9ea8e2cd227fa7e5a8a/node_modules/bcrypt
> node-pre-gyp install --fallback-to-build
make: Entering directory '/tmp/build_44931d5da2ada9ea8e2cd227fa7e5a8a/node_modules/bcrypt/build'
CC(target) Release/obj.target/nothing/../node-addon-api/src/nothing.o
AR(target) Release/obj.target/../node-addon-api/src/nothing.a
COPY Release/nothing.a
CXX(target) Release/obj.target/bcrypt_lib/src/blowfish.o
CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt.o
CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt_node.o
SOLINK_MODULE(target) Release/obj.target/bcrypt_lib.node
COPY Release/bcrypt_lib.node
COPY /tmp/build_44931d5da2ada9ea8e2cd227fa7e5a8a/node_modules/bcrypt/lib/binding/napi-v3/bcrypt_lib.node
TOUCH Release/obj.target/action_after_build.stamp
make: Leaving directory '/tmp/build_44931d5da2ada9ea8e2cd227fa7e5a8a/node_modules/bcrypt/build'
> nodemon#2.0.2 postinstall /tmp/build_44931d5da2ada9ea8e2cd227fa7e5a8a/node_modules/nodemon
> node bin/postinstall || exit 0
Love nodemon? You can now support the project via the open collective:
> https://opencollective.com/nodemon/donate
added 332 packages in 24.401s
-----> Build
Running heroku-postbuild
> server#1.0.0 heroku-postbuild /tmp/build_44931d5da2ada9ea8e2cd227fa7e5a8a
> NPM_CONFIG_PRODUCTION=false npm install --prefix client && npm run build --prefix client
> core-js#3.6.4 postinstall /tmp/build_44931d5da2ada9ea8e2cd227fa7e5a8a/client/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"
added 15 packages from 14 contributors and audited 1360 packages in 9.661s
2 packages are looking for funding
run `npm fund` for details
found 261 low severity vulnerabilities
run `npm audit fix` to fix them, or `npm audit` for details
> client#0.1.0 build /tmp/build_44931d5da2ada9ea8e2cd227fa7e5a8a/client
> vue-cli-service build
sh: 1: vue-cli-service: not found
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! client#0.1.0 build: `vue-cli-service build`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the client#0.1.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /tmp/npmcache.Bldog/_logs/2020-07-03T02_19_47_442Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! server#1.0.0 heroku-postbuild: `NPM_CONFIG_PRODUCTION=false npm install --prefix client && npm run build --prefix client`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the server#1.0.0 heroku-postbuild script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /tmp/npmcache.Bldog/_logs/2020-07-03T02_19_47_458Z-debug.log
-----> Build failed
We're sorry this build is failing! You can troubleshoot common issues here:
https://devcenter.heroku.com/articles/troubleshooting-node-deploys
Some possible problems:
- Node version not specified in package.json
https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version
Love,
Heroku
! Push rejected, failed to compile Node.js app.
! Push failed
Build finished
heroku.com
I couldn't find a solution for my particular situation that dealt with 'vue-cli-service' not found, so I'm asking here.
EDIT:
root folder package.json
"dependencies": {
"bcrypt": "^4.0.1",
"cors": "^2.8.5",
"dotenv": "^8.2.0",
"express": "^4.17.1",
"express-session": "^1.17.0",
"express-validator": "^6.4.0",
"mongoose": "^5.9.10",
"morgan": "^1.9.1",
"node-cron": "^2.0.3",
"nodemailer": "^6.4.6",
"passport": "^0.4.1",
"passport-local": "^1.0.0",
"puppeteer": "^3.0.1"
},
"devDependencies": {
"concurrently": "^5.2.0",
"nodemon": "^2.0.2"
}
client folder package.json
"dependencies": {
"#vue/cli": "^4.4.6",
"axios": "^0.19.2",
"core-js": "^3.6.4",
"fs": "0.0.1-security",
"lodash": "^4.17.15",
"vue": "^2.6.11",
"vue-router": "^3.1.5",
"vuetify": "^2.2.14",
"vuex": "^3.1.3",
"vuex-persist": "^2.2.0",
"websocket-extensions": "^0.1.4"
},
"devDependencies": {
"#vue/cli-plugin-babel": "^4.2.0",
"#vue/cli-plugin-eslint": "^4.2.0",
"#vue/cli-service": "^4.4.6",
"babel-eslint": "^10.0.3",
"eslint": "^6.7.2",
"eslint-plugin-vue": "^6.1.2",
"node-sass": "^4.13.1",
"sass": "^1.19.0",
"sass-loader": "^8.0.2",
"vue-cli-plugin-vuetify": "^2.0.5",
"vue-template-compiler": "^2.6.11",
"vuetify-loader": "^1.3.0"
}
I assume that You have installed Heroku CLI, logged in and connected to Your github account.
If so this is how I've deployed my project.
...
I have created a new branch i.e. deployBranch
Then in the frontend folder I have run 'npm run build'.
I have copied the 'dist' folder to project folder.
In backend file (server.js or in your case app.js) I have added this code just after the routes:
const trajectory = path.resolve();
if (process.env.NODE_ENV === "production") {
app.use(express.static(path.join(trajectory, "/dist")));
app.get("*", (req, res) =>
res.sendFile(path.resolve(trajectory, "dist", "index.html"))
);
}
(don't add heroku-postbuild script to package.json and delete /dist from .gitignore file in master project folder if there is one)
After this I commited all the changes to a new branch.
git push --set-upstream origin deployBranch
Then in heroku, i have created the new project.
In deploy section 'App connected to GitHub' I have connected it to my project github repo.
I've changed the branch to deployBranch in 'Manual deploy' and choose 'deploy branch'
After that all that was left to do was to add config vars in the settings from .env

Error installing node-sass dependency

I am trying to npm install a package.json with the following dependencies:
"devDependencies": {
"browser-sync": "^2.8.2",
"del": "^1.2.0",
"gulp": "^3.9.0",
"gulp-autoprefixer": "^2.3.1",
"gulp-babel": "^5.2.0",
"gulp-concat": "^2.6.0",
"gulp-eslint": "^1.0.0",
"gulp-filesize": "0.0.6",
"gulp-header": "^1.2.2",
"gulp-imagemin": "^2.3.0",
"gulp-jshint": "^1.11.2",
"gulp-livereload": "^3.8.0",
"gulp-minify-css": "^1.2.0",
"gulp-newer": "^0.5.1",
"gulp-notify": "^2.2.0",
"gulp-plumber": "^1.0.1",
"gulp-rename": "^1.2.2",
"gulp-sass": "^2.0.4",
"gulp-sourcemaps": "^1.5.2",
"gulp-svgmin": "^1.2.0",
"gulp-svgstore": "^5.0.4",
"gulp-uglify": "^1.2.0",
"imagemin-pngquant": "^4.1.2"
},
"dependencies": {
"node-sass": "^3.2.0"
}
But it fails with the node-sass package.
A part of the output is this:
Cannot download "https://github.com/sass/node-sass/releases/download/v3.2.0/darwin-x64-51_binding.node": HTTP error 404 Not Found
And then:
node-sass#3.2.0 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass#3.2.0 postinstall script 'node scripts/build.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node scripts/build.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs node-sass
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls node-sass
npm ERR! There is likely additional logging output above.
Node version 7.5.0 and npm version 4.1.2, OSX Sierra
Any suggestions?
I had same issue using node 8.1.3. I solved downgrading to latest long term supported version of nodejs (now is the 6.11.0).
The problem is that node-sass doesn't supports some nodejs versions....