Skip to content

gulp-sass is distracted by the .css and .scss files in the distribution #887

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

Closed
autopulous opened this issue Jul 20, 2016 · 1 comment
Closed
Assignees
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@autopulous
Copy link

Bug, feature request, or proposal:

Proposal or this may just be a question (assuming that my ignorance can be dispelled)...

What is the desired behavior?

Separation of the .css and .scss files in the npm distribution

What is the current behavior?

events.js:160
      throw er; // Unhandled 'error' event
      ^
Error: src\framework\ui\style.scss
Error: It's not clear which file to import for '@import "default-theme"'.
       Candidates:
         _default-theme.scss
         _default-theme.css
       Please delete or rename all but one of these files.
        on line 1 of src/framework/ui/style.scss

What are the steps to reproduce?

Use 'gulp' + 'gulp-sass' to build an Angular2 application using Material2

What is the use-case or motivation for changing an existing behavior?

gulp-sass appears to have no way of ignoring the .css files when building a Material application

Which versions of Angular, Material, OS, browsers are affected?

2.0.0-alpha.6

Is there anything else we should know?

I once kissed a Libertarian and liked it...

@jelbourn jelbourn added the P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent label Jul 26, 2016
@jelbourn jelbourn self-assigned this Jul 26, 2016
@jelbourn jelbourn closed this as completed Apr 9, 2017
@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 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Projects
None yet
Development

No branches or pull requests

2 participants