You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yep, the issue is that scss isn't a plugin, it's a syntax, so the postcss semantics are different, the syntax gets passed in as part of the process options. However in this project we can't change the options. To resolve this I've forked and manually added the ability to pass options. Was hoping to get the conversation started around extending this project to deal with options as well.
@alexisvincent Excited to hear that you found a workaround! I'm not using JSPM myself, but am curious as to how you were able to pass in your processOptions. I was looking to use SCSS with TypeScript in Webpack while getting around a current issue with typings-for-css-modules-loader using this article, but haven't been able to pass in syntax option.
@jessicamindel Oh boy! This was soo long ago I can barely remember anything about it. Issues around JSPM and SystemJS were largely that all this loading had to happen in the browser, rather than serverside. I'm sorry, but I'm going to be of absolutely no use. Good luck though!
tell me what is the best approach for this. the scss processor works well with css, and in case that some scss appear, we can parse it with the same syntax processor also we can allow send some custom syntax.
Or even better and forget all about send plugins or syntax and try to support the use of postcss.config.js file.
Activity
joshwnj commentedon May 30, 2016
@alexisvincent are you using something like webpack or browserify? There are some examples of using CSS Modules alongside other postcss plugins:
alexisvincent commentedon May 30, 2016
@joshwnj Nope, trying to use this project to fix up the JSPM loader.
joshwnj commentedon May 31, 2016
@alexisvincent ah ok. Have you seen the jspm demo?
I'm not very familiar with JSPM myself but if I were looking I would start by trying to add the
postcss-scssplugin to the beginning of the plugin array here: https://github.com/geelen/jspm-loader-css-modules/blob/master/index.js#L3-L9alexisvincent commentedon May 31, 2016
Yep, the issue is that scss isn't a plugin, it's a syntax, so the postcss semantics are different, the syntax gets passed in as part of the process options. However in this project we can't change the options. To resolve this I've forked and manually added the ability to pass options. Was hoping to get the conversation started around extending this project to deal with options as well.
jessicamindel commentedon Jan 15, 2019
@alexisvincent Excited to hear that you found a workaround! I'm not using JSPM myself, but am curious as to how you were able to pass in your processOptions. I was looking to use SCSS with TypeScript in Webpack while getting around a current issue with
typings-for-css-modules-loaderusing this article, but haven't been able to pass in syntax option.alexisvincent commentedon Jan 16, 2019
@jessicamindel Oh boy! This was soo long ago I can barely remember anything about it. Issues around JSPM and SystemJS were largely that all this loading had to happen in the browser, rather than serverside. I'm sorry, but I'm going to be of absolutely no use. Good luck though!
alexisvincent commentedon Jan 16, 2019
I don't think this project has kept up to date though, so you might have more luck elsewhere.
nathanredblur commentedon Oct 3, 2019
I think you can add some param to support scss syntax like:
css-modules-loader-core/src/index.js
Line 18 in 3d83770
tell me what is the best approach for this. the scss processor works well with css, and in case that some scss appear, we can parse it with the same syntax processor also we can allow send some custom syntax.
Or even better and forget all about send plugins or syntax and try to support the use of postcss.config.js file.