-
Notifications
You must be signed in to change notification settings - Fork 5
Not working anymore :( #4
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
Comments
It appears to be trying to parse the file as a js |
Yeah damn. The new JSPM dropped yesterday and I haven't had a chance to fix this yet. Soon though! You can try to roll back to JSPM |
Ok thanks mate. I'll give it a shot On Thu, 20 Aug 2015 19:13 Glen Maddern notifications@github.com wrote:
|
Hey @whitneyit — I've pulled together a working example that covers CSS Modules, jspm-css-loader with plugins like PostCSS, and vanilla CSS. You can see it here: It also uses the |
Awesome thanks man I'll check it out! On Thu, 20 Aug 2015 23:28 Charlie Gleason notifications@github.com wrote:
|
By updating * jspm-loader-css-modules to version 1.0.1-beta1 * jspm-loader-css to version 1.0.1-beta1 Note that due to a bug in SystemJS, one has to modify the file jspm_packages/npm/postcss@5.0.10/lib/parse.js so that a module isn't required in a string. In other words, line 14 has to be changed to something like this (just removing the require statement is enough) throw new Error('Option safe was removed. ' + 'Use parser: "postcss-safe-parser"'); Fixes css-modules#4 css-modules#6 css-modules#7
Cloning this repo and running
jspm install
yields the following error.The text was updated successfully, but these errors were encountered: