-
-
Notifications
You must be signed in to change notification settings - Fork 156
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
CRA bundling error for extract-files #118
Comments
Same here, upon upgrading to the new react-scripts v2.0.0 (Babel 7, webpack 4, Jest 23): The build works, but the website fails with:
Let me know if there is more info I can provide. And thanks for your efforts on these libraries that keep us on the right side of sanity in the crazy JS world ;-) |
This is a CRA bug, not an issue with Here is an example of what it should look like: https://github.com/zeit/next.js/blob/7.0.1-canary.0/build/webpack.js#L155 This is a similar issue to #117. Don't worry, I'm sure they will fix it because their flawed config will result in bundling errors for other dependencies too, such as |
Yep, seems to be fixed in react-scripts@2.0.1, apologies for the overhead! |
FYI, the import works now, but the library still runs into an issue when trying to access functionality from
Which points to line 54 in var files = extractFiles(body); I assume after failing to fullfill the require in line 16: var _require3 = require('extract-files'),
extractFiles = _require3.extractFiles,
ReactNativeFile = _require3.ReactNativeFile; I'm guessing this is still an incompatibility between the latest CRA tooling and the require / import statements or is something else happening here? Final note: I am also using Thanks again! |
Here is the discussion about the final version of react-scripts: |
Not sure what you mean, the dependency is precompiled: https://registry.npmjs.org/extract-files/-/extract-files-4.0.0.tgz |
Having the same issue as @dirkdevriendt. |
Indeed, I think, as @jaydenseric indicates, it's really about the .mjs extension. I "fixed" it by renaming all *.mjs files to *.js in my local version of the :-) This may again have caused other issues down the line, but where would the fun be if that didn't happen... |
FYI: my current understanding is that CRA is waiting on Jest support which is waiting on esm support... |
Next.js does not support |
Yes, very unfortunate that it does not work now any more. |
They fixed it in 2.0.4 |
I tried to update and got an error.
The text was updated successfully, but these errors were encountered: