-
Notifications
You must be signed in to change notification settings - Fork 47
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
Node SASS 5.0.0 #193
Node SASS 5.0.0 #193
Conversation
Bumps [node-sass](https://github.com/sass/node-sass) from 4.14.1 to 5.0.0. - [Release notes](https://github.com/sass/node-sass/releases) - [Changelog](https://github.com/sass/node-sass/blob/master/CHANGELOG.md) - [Commits](sass/node-sass@v4.14.1...v5.0.0) Signed-off-by: dependabot[bot] <support@github.com>
we have upgraded to node-sass-5.0.0 which only supports Node 14.15.4 and above, this commit bumps our overall minimum supported version to 14.15.4
Build is failing, so even more investigation is needed. Will pick this up when I have time. Otherwise, if anyone else is at a loose end, please feel free 🙂 |
After some more investigating, it turns out that
This is caused by an issue in sass-loader which would not allow versions greater than 4 of node-sass to be used. It has been fixed in sass-loader v10.0.5, however two of our dependencies use older versions as sub dependencies:
One approach here could be to manually change these sub dependencies in package-lock.json, although I’d worry about bumping the one in Storybook as it’s two major versions behind. Alternatively we could stay on node-sass 4.14.1 until sass-loader is updated in both places. |
I can't find In any case, I think the main issue is the storybook package so I would be ok to stay on |
You can only really modify transient dependencies in the package-lock if they are within the accepted range, otherwise they get overwritten. So in the case of the angular storybook one its pinned to major version 8 by the caret'^'. This prevents us accidentally mixing incompatible versions, but it does sadly rule out this approach.
i noticed that our angular-devkit dependency is also out of date, I believe the version should reflect the Angular build we are on, e.g. |
I raised a separate PR for the angular-devkit upgrade, but I'm not too sure what to do about this one. It may be we have to hold fire until we can finally tackle #35 |
Excellent, thanks for raising that PR @thatguynamedandy 👍 I'll create an issue to track the update to Node v5.0.0 and close this PR. |
Description
This replaces the Dependabot PR to bump Node SASS to 5.0.0.
A breaking change in Node SASS 5.0.0 requires a minimum Node version 14.5.4.
I updated to Node v14.15.4 and ran the build, it completed without errors 👍 .
However, when I ran
npm run start
, the following warnings appeared, which may need some investigation when time allows. An issue on the Node repo suggests using the--trace-warnings
flag help pin point it.In DRAFT status as the following warnings still need invesigation.