Skip to content

build: avoid installing node-sass #22283

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

Merged
merged 1 commit into from
Mar 19, 2021

Conversation

crisbeto
Copy link
Member

We no longer use node-sass, but we were still installing it, because gulp-sass depends upon it. These changes switch to a fork of gulp-sass that depends on the Dart version of Sass.

We no longer use `node-sass`, but we were still installing it, because `gulp-sass`
depends upon it. These changes switch to a fork of `gulp-sass` that depends on
the Dart version of Sass.
@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent merge safe target: patch This PR is targeted for the next patch release labels Mar 18, 2021
@crisbeto crisbeto requested a review from a team as a code owner March 18, 2021 17:19
@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Mar 18, 2021
Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Mar 18, 2021
Copy link
Contributor

@Splaktar Splaktar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like https://www.npmjs.com/package/gulp-dart-sass is getting some good usage and installation growth, but it's too bad that the repo hasn't been updated since October and doesn't accept issues (only PRs).

It's good to get off of node-sass for sure, but it isn't clear that this new package will be something that we can rely upon long-term.

@andrewseguin
Copy link
Contributor

Needs rebase to get it into 11.2.x

@andrewseguin andrewseguin added target: minor This PR is targeted for the next minor release and removed target: patch This PR is targeted for the next patch release labels Mar 19, 2021
@andrewseguin andrewseguin merged commit 902e946 into angular:master Mar 19, 2021
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Apr 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: minor This PR is targeted for the next minor release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants