Closed nybblr closed 7 years ago
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 package.json
prevents the lookup behavior:
"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 - https://github.com/yarnpkg/yarn/issues/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?