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
{{ message }}
Repository navigation
WP Build: Page crashes with "Element type is invalid" error. #75440
After this PR wp-build pages are breaking with the following message:
Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.
Check the render method of `RootSinglePage`.
Could it be some interplay between the two changes? We've been working with #73379 in the WP build for a while now already, and it works fine. With Gutenberg enabled, things work as long as I revert #75387 locally, but otherwise it breaks.
@ellatrix Tested with both minimal setup and Jetpack Forms (feature flag add_filter('jetpack_forms_alpha', '__return_true');) and seeing the same issue still.
@ellatrix@youknowriad Tested #75460 with the minimal setup and the issue persists. You are right in the discussion, though, so I opened this draft to test the relative import priorities and that works for me with the minimal setup.
Activity
ellatrix commentedon Feb 12, 2026
This sounds like either an issue with
wp-buildor npm packages to me (but we haven't published stable npm packages since that commit).But it also seems like you're overriding the private API's global? Is that expected? https://github.com/dhasilva/minimal-wp-build-test/blob/trunk/build/scripts/private-apis/index.js
I don't know anything about
wp-build, would love to have help from others familiar with it.ellatrix commentedon Feb 12, 2026
Could be related to #73379, which started bundling
private-apisinwp-build, cc @youknowriadsimison commentedon Feb 12, 2026
Could it be some interplay between the two changes? We've been working with #73379 in the WP build for a while now already, and it works fine. With Gutenberg enabled, things work as long as I revert #75387 locally, but otherwise it breaks.
ellatrix commentedon Feb 12, 2026
Well yes, it's because there's been no private API additions since then so the file is the same as core's
ellatrix commentedon Feb 12, 2026
#75460 could fix it I think, could you test it?
simison commentedon Feb 13, 2026
@ellatrix Tested with both minimal setup and Jetpack Forms (feature flag
add_filter('jetpack_forms_alpha', '__return_true');) and seeing the same issue still.dhasilva commentedon Feb 18, 2026
@ellatrix @youknowriad Tested #75460 with the minimal setup and the issue persists. You are right in the discussion, though, so I opened this draft to test the relative import priorities and that works for me with the minimal setup.
dhasilva commentedon Mar 18, 2026
wp-build now does not bundle anything: #75987