[wp-trac] [WordPress Trac] #64393: Change how we include Gutenberg in Core
WordPress Trac
noreply at wordpress.org
Tue Jan 20 00:14:59 UTC 2026
#64393: Change how we include Gutenberg in Core
------------------------------+--------------------------
Reporter: youknowriad | Owner: youknowriad
Type: task (blessed) | Status: reopened
Priority: high | Milestone: 7.0
Component: Build/Test Tools | Version:
Severity: blocker | Resolution:
Keywords: has-patch | Focuses:
------------------------------+--------------------------
Comment (by dmsnell):
I’ve proposed in [https://github.com/WordPress/wordpress-
develop/pull/10761 PR#10761] a revert of the changes to remove the parser
from Core. Ironically, the parser files were previously being copied in
the same exact way as they are in this updated build, but by `webpack`
instead of a new generated script. This ticket //did not have to change
the way the parser is maintained// and really should be handled in another
ticket: that ticket is #64521. Perhaps it would have been less disruptive
to either not address the parser question in this ticket (since it wasn’t
necessary or related to the other changes) or to have made the structural
changes first before attempting it.
While reviewing the changes in [https://github.com/dmsnell/wordpress-
develop/pull/27 dmsnell#27] I noticed also that we are attempting to
manually parse PHP code using regular expressions and basic parsing in JS,
even though we should have PHP available. @youknowriad did you consider
using PHP to evaluate the files and return a reliable JSON-serialization
of their data?
--
Ticket URL: <https://core.trac.wordpress.org/ticket/64393#comment:114>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list