-
Notifications
You must be signed in to change notification settings - Fork 19
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
Cannot resolve fibers in optimism #6
Comments
What version of |
Got this also with [email protected] |
What bundler are you using? Webpack? Rollup? Something else? The import of Lines 11 to 18 in 84624ab
Please feel free to provide any more information that seems relevant. |
I'm using Webpack. It is just a warning I guess this post can serve to that others won't be concerned about it when searched it online. I'm not sure how other lib handle things like this, or maybe there's something wrong with my webpack config? yarn said the following:
|
Webpack also. Thanks. |
Got the warning too, using |
I see the same warning - also using apollo inmemory cache. Looks like |
This happens with webpack >= 4.16.2: https://github.com/webpack/webpack/releases/tag/v4.16.2 Here is an related issue: webpack/webpack#7777 |
Any plan on fixing it? |
Does everyone understand the point of the code in question? The goal is to import We've already "fixed" this sort of problem once before, but I suppose we will have to keep working around Webpack's unsound and incomplete attempts to statically analyze this code. |
This approach (just published in Line 12 in 5cc2edd
Your move, Webpack. But also… could you just… not? 😂 |
WARNING in ./node_modules/optimism/lib/local.js
Module not found: Error: Can't resolve 'fibers' in '/Users/***/node_modules/optimism/lib'
@ ./node_modules/optimism/lib/local.js
@ ./node_modules/optimism/lib/index.js
@ ./node_modules/apollo-cache-inmemory/lib/optimism.js
@ ./node_modules/apollo-cache-inmemory/lib/readFromStore.js
@ ./node_modules/apollo-cache-inmemory/lib/index.js
The text was updated successfully, but these errors were encountered: