-
-
Notifications
You must be signed in to change notification settings - Fork 899
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
Module not found: Error: Can't resolve 'babel-runtime/regenerator' #310
Comments
I guess you could For the time being, |
I notified Mozilla about missing dependency in mozilla/pdf.js#10280. |
I have a similar issue. If I add babel-runtime manually it causes an issue with duplicate packages because there is babel-runtime/regenerator and @babel/runtime/regenerator. My build only succeeded when I went into pdfjs and manually pasted the path to my @babel/runtime/regenerator. I think the less hacky hack would be to use webpack aliasing to resolve the right runtime-regenerator, but I can't figure that out. I guess I'm wondering if there's some other way to address this. |
Hi all, |
Related to #310 To be rolled back after PDF.js 2.1.x release
Thanks @wojtekmaj. We encountered the same issue today and did |
We also experienced same issue today. Using |
@allanchua101 that is the best way to work around it ;) Mozilla is about to release a new version of PDF.js though, so this workaround should no longer be needed soon. |
All, React-PDF 4.0.3 is out and should have this issue resolved. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
****** My error : This dependency was not found:
To install it, you can run: npm install --save babel-runtime/regenerator ****** after I run the commad => npm i --save-dev babel-runtime It works for me |
Hi,
I'm facing build error propably due to babel versions conflict.
This is output from Webpack:
I found this issue mozilla/pdf.js#10280 so if I get it right this will be fixed with new version of pdfjs-dist.
But according to info/issues on react-pdf project it seems that for some people it is already working now with pdfjs-dist 2.0.943. Is there any additional step to make this working?
Environment
Regards
Michal
The text was updated successfully, but these errors were encountered: