-
Notifications
You must be signed in to change notification settings - Fork 32
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
NodeJs compatibility #54
Comments
dawnmist
added a commit
to dawnmist/dota-stats-ui
that referenced
this issue
Mar 9, 2020
dawnmist
added a commit
to dawnmist/dota-stats-ui
that referenced
this issue
Mar 9, 2020
Same issue here, seems to come from deasync loopWhile. |
Deasync is no longer a dependency. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey all, I was working with this plugin on the node version 12.15.0 and over there it wasn't working... by downgrading to 12.4.0 it did work. Met me post more details soon, but any suggestions where this is coming from?
The issue I encountered was that the webpack build kept spinning reaching some of the first encountered styled-components. repeatedly the same file. (implementation of the component made no difference). simple for example: styled.div with background color
also running the test directly in the repo seems to be broken?
after this test i downgraded to node 11.9.0 via nvm. result is that jest is run within seconds!
checking versions it seems like version 12.10 is correct, higher is broken. confirmed 12.11.0 is not working, (12.11.1 also broken )
locally I updated all packages (including jest, and styled components helpers for version 5) but didn't help me any further...
looks like postcss.process.then neither . catch is being triggered:
https://github.com/trevorburnham/babel-plugin-namespace-styled-components seems to be having the same issue
The text was updated successfully, but these errors were encountered: