-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Polyfill error after 1.17.1
upgrade
#6644
Comments
Getting something similar:
|
Getting this same error for a library which uses axios |
I'm also getting the same error after I added:
|
This will be fixed by #6562 |
@MichaelDeBoey that was already merged and is on version |
@brandonpittman Could you share a minimal repro? |
I'm not sure what kind of repro I can do. It's a work system that processes brain scan images using dicom-parser. dicom-parser is the library that's using zlib under the hood. |
Hey @brandonpittman, I've been battling this same issue with the same error and just tracked it down to the |
@scottwillman Seems to be this require of |
I'm confident this issue is fixed due to my upstream PR: imranbarbhuiya/esbuild-plugins-node-modules-polyfill#120. If you can get your project to resolve to esbuild-plugins-node-modules-polyfill@v1.1.0, can you let me know if it solves your issue? |
@markdalgleish I updated to 1.18 and 1.1.0 of the polyfills package seems to be getting resolved…and the error is gone. I think we can say this issue is solved. |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
What version of Remix are you using?
1.17.1
Are all your remix dependencies & dev-dependencies using the same version?
Steps to Reproduce
1.17.1
require
in a moduleExpected Behavior
Shouldn't trigger error
Actual Behavior
Triggers an error like this:
Rolling back to
1.17.0
makes the error go away.The text was updated successfully, but these errors were encountered: