Add npm org scope to WordPress dependencies #2172
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related: #941
Related: #1205
This pull request seeks to add the WordPress npm organization scope to all WordPress dependency imports. It is a further realization of the intent for these top-level folders to be distributed as independent packages.
Other side-benefits include:
wp_register_script
script dependenciesImplementation notes:
This will be hellish to rebase, so I'd prefer not to let this one linger.
Testing instructions:
This is difficult to test because it touches nearly every file in the application. Verify through
npm run build
,npm run dev
,npm test
that no errors occur, and that no regressions or console errors occur by thorough use of the application.