Skip to content
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

Bugfix: inconsistent handling of webpack virtual modules #1346

Merged
merged 6 commits into from
Feb 1, 2023

Conversation

ef4
Copy link
Contributor

@ef4 ef4 commented Jan 30, 2023

This should match the pattern we use when emitting virtual modules.

It works sometimes as it was, but not reliably. This change seems to make the tests pass every time.

@ef4
Copy link
Contributor Author

ef4 commented Jan 30, 2023

I think we're having sporadically bad interactions between webpack-virtual-modules and thread-loader. I had reproduced the problem without thread-loader present so I thought I ruled that out, but apparently not.

This replaces webpack-virtual-modules with our own loader. Ours can be simpler because we can make it stateless.

This also involved a larger change to where we tap into webpack. The previous location was unable to redirect to a new loader. This new solution gives us better control.
@ef4 ef4 merged commit 22d54eb into main Feb 1, 2023
@ef4 ef4 deleted the bugfix-webpack-vfs branch February 1, 2023 20:22
This was referenced May 2, 2023
@ef4 ef4 added the bug Something isn't working label May 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant