-
Notifications
You must be signed in to change notification settings - Fork 22
Local .babelrc breaks scss-tokenizer #10
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
Ahh, this might also do the trick: https://babeljs.io/docs/usage/babelrc/#lookup-behavior I'll test adding this option locally and see if it works. |
Ah, since this is using an older version of Babel, adding this to scss-tokenizer's "babel": {
"breakConfig": true
} Quick PR, or is there another PR in progress that will fix this issue? |
Having the same issue. I have temporarily resolved it by forking node-sass to use a 2.1.1 dependency for sass-graph instead of ^2.1.1 . It appears sass-graph was updated yesterday and that's when this library as added as a dependency. The blessings and curses of the npm ecosystem :) |
Thanks all. I unpublished sass-graph 2.2.0 but for some reason people were still getting it. Looks like there may be an issue for yarn users - yarnpkg/yarn#3274 Testing #11 locally before publishing a new release. |
Thanks all! |
I just clean installed node-sass (same patch version I think) and through a dependency of a dependency it now includes scss-tokenizer. I'm getting this cryptic error:
I tried a few things, then nuked my local
.babelrc
config andnode-sass
worked. So my guess isscss-tokenizer
is using my local .babelrc automatically?Perhaps adding an explicit config to this package would prevent that?
The text was updated successfully, but these errors were encountered: