Closed renich closed 3 years ago
OK, the fix is a bit more complicated.
First, had to update every dependency. Current versions are:
"devDependencies": {
"@babel/core": "^7.13.16",
"@babel/preset-env": "^7.13.15",
"babel-loader": "^8.2.2",
"clean-webpack-plugin": "^3.0.0",
"css-loader": "^5.2.4",
"file-loader": "^6.2.0",
"html-webpack-plugin": "^5.3.1",
"mini-css-extract-plugin": "^1.5.0",
"node-sass": "^5.0.0",
"sass-loader": "^11.0.1",
"webpack": "^5.34.0",
"webpack-cli": "^4.6.0",
"webpack-merge": "^5.7.3"
},
"dependencies": {
"bootstrap": "^4.6.0",
"jquery": "^3.6.0",
"popper.js": "^1.14.6"
}
Also, had to modify: config/webpack/development.js
and replace the webpack-merge line with:
const { merge } = require('webpack-merge');
Then, a subsequent npm update
to update the dependencies. After that, just run amber w
and it should work.
That did it. It works fine now.
Fixed with #1258
Description
When using the aforementioned versions, when trying to use
amber watch
, npm fails to build node-sass.Steps to Reproduce
amber new -d sqlite someproj
cd $_; shards install --ignore-crystal-version
crystal w
Expected behavior: [What you expect to happen] It should just build successfully.
Actual behavior: [What actually happens] It fails to build node-sass.
Reproduces how often: [What percentage of the time does it reproduce?] This happens every time.
Versions
Amber: Amber CLI (amberframework.org) - v0.36.0 OS: Fedora 34 beta node: v15.11.0 npm: v7.6.0
Additional Information
The fix is simple enough. Just update the node-sass requirement in
package.json
to^5.0.0
. Here're the notes upstream: https://openbase.com/js/node-sass/versions