You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Multiple entry-points from the same files entry have common dependency.
Now one of the entry point may depend on say wp-blocks, but not the other. In this
case with current approach, we add wp-blocks to every entry chunks, including runtime, vendor etc.
So depending on which entry-point we have called first, additional external WordPress dependencies might come to the page where it shouldn't.
To solve this, we can
Split files entry through multi-compiler mode where we know that none of them share anything common.
Or just add the external WP dependencies to the last chunk of an entry-point.
I am not sure if 2 should be a good approach here. Because in theory, the vendor could have external dependency too.
The text was updated successfully, but these errors were encountered:
Multiple entry-points from the same files entry have common dependency.
Now one of the entry point may depend on say
wp-blocks
, but not the other. In thiscase with current approach, we add
wp-blocks
to every entry chunks, includingruntime
,vendor
etc.So depending on which entry-point we have called first, additional external WordPress dependencies might come to the page where it shouldn't.
To solve this, we can
I am not sure if
2
should be a good approach here. Because in theory, thevendor
could have external dependency too.The text was updated successfully, but these errors were encountered: