Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
CKEditor 5 has its own build process. This should be integrated with the core build process in preparation to being moved to core.
See #3 for more nuance.
Proposed resolution
Combine package.json
, js/admin/package.json
, and js/drupal/package.json
into a single package.json
file which can be moved to the core/package.json
in the MR that adds CKEditor 5 to core.
Issue fork ckeditor5-3227857
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
Wim LeersIf I'm not mistaken, this means expanding this in
core/package.json
:So probably that means adding
build:ckeditor5
?Does this have other implications too?
Comment #3
lauriiiThat will be one of the changes required. However, we might have to look deeper than that because at the moment, we have three package.json files in the module:
package.json
,js/admin/package.json
, andjs/drupal/package.json
. Drupal core has a single package.json file for all of core. Ideally we would be able to move contents of all three files to that package.json.Comment #5
lauriiiComment #6
Wim LeersThat fixed it! :D
But now there's a different failure:
How … is that even possible?! Line 5 … did not change. Must be a new upstream requirement… yep: #2591827: Add YAML linting to core coding standards checks
Fixed in d22d96beddade3200a9aed82504393593542903d.
Comment #7
Wim LeersGreen!
What's next here, @lauriii?
Comment #8
Wim LeersApparently nothing, so ready for final review from @bnjmnm!
Comment #10
Wim LeersComment #12
bnjmnmFeedback addressed, good consolidations!