Skip to content
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

build: switch to dart-sass #12370

Merged
merged 1 commit into from
Jul 29, 2018

Conversation

devversion
Copy link
Member

@devversion devversion commented Jul 25, 2018

  • Switches to dart-sass in order to be consistent with the Bazel output. That way we can identify potential issues with the SASS output (e.g. demo-app) before we at some point make the full-switch.
  • Also speeds-up the project installs because libsass bindings are no longer needed (trade-off with compilation time though; but pretty minimal due to our amount of Sass files)

@devversion devversion requested a review from jelbourn as a code owner July 25, 2018 14:42
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jul 25, 2018
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

FYI @nex3

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker target: major This PR is targeted for the next major release and removed target: master only labels Jul 25, 2018
@nex3
Copy link

nex3 commented Jul 25, 2018

Note that if you can configure the task to run the synchronous version of Dart Sass, it'll be substantially faster.

@jelbourn jelbourn removed the action: merge The PR is ready for merge by the caretaker label Jul 25, 2018
@jelbourn
Copy link
Member

Right, I forgot about that. @devversion we should look into that

@jelbourn jelbourn added the action: merge The PR is ready for merge by the caretaker label Jul 25, 2018
* Switches to dart-sass in order to be consistent with the Bazel output. That way we can identify potential issues with the SASS output (e.g. demo-app) before we at some point make the full-switch.
* Also speeds-up the project installs because libsass bindings are no longer needed (trade-off with compilation time though; but pretty minimal due to our amount of Sass files)
@devversion devversion force-pushed the build/switch-to-dart-sass branch from c2f19df to 58b94a3 Compare July 25, 2018 22:01
@devversion
Copy link
Member Author

@nex3 @jelbourn Should be fine now. Please have another look.
Also fixed that the commit message mentioned "consistency with gulp", while it should be actually "consistency with Bazel"

Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

@mmalerba mmalerba merged commit e074003 into angular:master Jul 29, 2018
@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 Sep 9, 2019
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 target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants