Build: Include entire lib/
folder in plugin bundle
#20736
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.
This pull request seeks to resolve an issue where warnings are logged in the Gutenberg 7.7.0 RC1 release.
The underlying cause is due to the fact that these files are not whitelisted for inclusion in the built plugin ZIP file. This has been a common source of issues in the past (see #20225, #19072, f09bb3e, #9799).
The proposed changes opt to include the entire
lib
folder, rather than add additional patterns to match these files. It's not clear by the initial introduction of this pattern in #985 whether there were any files intended to be omitted from this directory, since at the time all files would have been matched anyways.In the future, we should consider options for being more proactive in accounting for these errors. Specifically, we should try to incorporate the built plugin as part of the Travis build, perhaps as part of the end-to-end tasks (see #14289 (comment) and “Pregenerate the plugin build to use across tasks” task of #15159).
Testing Instructions:
Run
npm run bundle-plugin
.Verify that all expected files in
lib
are included: