-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Fatal concurrent map read and map write error when using the inject option #878
Comments
Thanks for the report. It looks like this regression may have been introduced all the way back in 0.8.21. The issue is that this was the first time the cached |
Thank you so much for the quick reply @evanw. Please let me know if I can be of any further help, such as testing the fix before releasing it or helping to reproduce it. |
I was able to reproduce it with the information you gave me. The fix will be out in the next release. I believe a workaround in the meantime is to specify entry points with either an absolute path (starting with |
Thanks a lot for the fast fix, this is fantastic! I also really appreciate the temporary workaround until then. Esbuild is a great project and in the hands of an amazing maintainer! 🥇 |
Hello! I have a Lerna monorepo in which each package runs its own esbuild process (version 0.8.51) to compile the React TypeScript code to CJS. I use the JavaScript API from esbuild with the following options:
Since I started using the inject option, I keep receiving the error which I included at the end of the ticket. However, this error appears very randomly, as it does not repeat in the same package within my monorepo, but rather keep showing up in a random one. When I turn off the inject option, it works just fine.
The content of my inject file look like this:
export {jsx} from '@emotion/react';
The same issue appears in #556, however this fix seems to be unrelated as without the inject option everything works well.
The error:
The text was updated successfully, but these errors were encountered: