-
-
Notifications
You must be signed in to change notification settings - Fork 866
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
Why 2 webpack instances? #778
Comments
Yes, you need to first build the client to ensure assets.json creation, because the server needs it to generate the HTML |
@hornta Multicompiler runs sync. Essentially it is doing the same thing Razzle is in that Razzle compiles the client then server. as @cloud-walker points out you need the assets built so even if you used the Multicompiler in parallel via third party module you'd still need to ensure the client it built. |
Hola! So here's the deal, between open source and my day job and life and what not, I have a lot to manage, so I use a GitHub bot to automate a few things here and there. This particular GitHub bot is going to mark this as stale because it has not had recent activity for a while. It will be closed if no further activity occurs in a few days. Do not take this personally--seriously--this is a completely automated action. If this is a mistake, just make a comment, DM me, send a carrier pidgeon, or a smoke signal. |
Hi. Is there a reason for having two separate webpack instances vs. using webpacks multicompiler(https://webpack.js.org/api/node/#multicompiler)
The text was updated successfully, but these errors were encountered: