-
Notifications
You must be signed in to change notification settings - Fork 139
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
Node 10.1.0, Chimp and fibers problem (can we upgrade fibers?) #690
Comments
You should downgrade node version to v8.10.0 |
well it works on 9.x right now, but just in general I'd like to advance with Node versions instead of downgrading and staying on older versions. |
+1 on this one. Problem suddenly occurred during our CI process today. |
Same problem over here. @joscha what's the current state. What's your workaround? |
No good workaround unfortunately - we will most likely resort to the custom resolutions that yarn offers and then see if we can get on chimp vNext asap |
Upgrading/resolving fibers to |
I take that back, this seems to work: index d0d1e12a40a..d2b41f8f023 100644
--- a/web/package.json
+++ b/web/package.json
@@ -159,7 +159,7 @@
- "node-gyp": "^3.6.2",
+ "node-gyp": "^3.7.0",
@@ -245,10 +245,13 @@
"resolutions": {
+ "chimp/fibers": "^2.0.2",
+ "chimp/**/fibers": "^2.0.2",
+ "chimp/fibers/node-gyp": "^3.7.0"
},
}
|
another resolution for
fixes it. That is quite widespread though, so might be worth waiting for it to be picked up separately by projects. |
@samhatoum any chance to get these deps bumped? |
@joscha does your workaround involve installing |
@Ziinc yes, see #690 (comment) |
This issue is being tracked in Chimpy |
Expected behaviour
Chimp installs as expected.
Actual behaviour
The
fibers
package fails to compile.Exact steps to reproduce / repository that demonstrates the problem
after install of chimp:
Version & tools:
chimp -v
0.51.1node -v
10.1.0uname -v
ubuntu xenialConsole / Log Output
Join our Slack xolv.io/community #chimp channel, where you can find help and help others.
The text was updated successfully, but these errors were encountered: