-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Error in production bundle: Incompatible receiver, Map required #4692
Comments
Thanks for the research. I've created a ticket at the But until Parcel 2 is released as the recommended release (non-alpha), I think it's worth fixing here as well. As a quick fix, we could make the deduping optional? Although it might be better to figure out how deduping is causing this. |
@smeijer aria-query can't be the only project in the dependency tree using |
I haven't verified, but that sounds plausible. |
The same problem is happening in a project that uses the latest Parcel 1.12.4 and parse 2.17.0. Project source code: https://github.com/majac91/Travel_journal - Exact commit |
Sorry to bump, but any news on this? same problem: I don't use |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. |
Just run into this in 2022, without I'm using |
🐛 bug report
When including
aria-query
in my project,parcel serve
works fine, butparcel build
will result in a non-working state. The app will throw🎛 Configuration (.babelrc, package.json, cli command)
package.json:
index.html:
index.js:
🤔 Expected Behavior
As the app is running just fine in
serve
mode, (logs a message to console), the app should also run when being build withparcel build
.😯 Current Behavior
An error is thrown:
💁 Possible Solution
I don't have the solution, but it looks like it has something to do with core-js and Map being poly-filled more than once? But I'm not sure.
🔦 Context
I need to include
aria-query
into my client side bundle, but so far I'm unable to doing so, because of the error that is present in the production bundle (but not when runningparcel serve
).💻 Code Sample
🌍 Your Environment
The text was updated successfully, but these errors were encountered: