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

Inline framework packages and check for react-dom/server usage #19

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

danilobuerger
Copy link

The framework test was changed in gatsby 5.6 via gatsbyjs/gatsby#37508

Therefor framework.test is no longer of type RegExp and fixFrameworkCache would return early. This resulted in the non-creation of framework-[contenthash].js. Instead the framework was then located in app-[contenthash].js

Since I didn't find a good way to get the framework bundles, I just inlined them from the gatsby repos. They were not changed since 2020 (the creation of the framework chunking). So this seems pretty stable.

Further this now checks for react-dom/server and does not include it in the framework bundle as done in the main gatsby repos by PR linked above.

\ cc @LekoArts Maybe you have the time to quickly glance over this?

The framework test was changed in gatsby 5.6 via gatsbyjs/gatsby#37508

Therefor framework.test is no longer of type RegExp and fixFrameworkCache would return early. This resulted in the non-creation of framework-[contenthash].js. Instead the framework was then located in app-[contenthash].js

Since I didn't find a good way to get the framework bundles, I just inlined them from the gatsby repos. They were not changed since 2020 (the creation of the framework chunking). So this seems pretty stable.

Further this now checks for react-dom/server and does not include it in the framework bundle as done in the  main gatsby repos by PR linked above.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant