-
Notifications
You must be signed in to change notification settings - Fork 2k
feat(build): Ignore compiled sass/less files from git #1592
Conversation
@@ -31,7 +31,7 @@ module.exports = { | |||
tests: ['public/lib/angular-mocks/angular-mocks.js'] | |||
}, | |||
css: [ | |||
'modules/*/client/css/*.css' | |||
'modules/*/client/{css,less,scss}/*.css' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How does this affect the less
& sass
settings below?
@@ -169,9 +169,6 @@ gulp.task('sass', function () { | |||
return gulp.src(defaultAssets.client.sass) | |||
.pipe(plugins.sass()) | |||
.pipe(plugins.autoprefixer()) | |||
.pipe(plugins.rename(function (file) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why was this removed?
@mleanos Now, both My proposal is to compile |
@shanavas786 Thank you. That perfectly answered my questions. Also, I agree with the goals of these changes. It's definitely gonna be easier to manage these compiled assets. @meanjs/contributors comments? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I haven't tested though, but the changes seem pretty straight forward.
Compiling
sass/less
files to<module>/client/css
directory makes it difficult to differentiate between compiled and raw css files.By compiling them to appropriate directories, compiled files can be easily ignored.