Add logic for block style entry points #390
Open
+34
−6
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 Issue/RFC: #339
This PR introduces several enhancements and fixes to the configuration and entry logic for the toolkit package. Key changes include the reorganization of path configurations, the addition of a new configuration option for loading block-specific styles, and the update of the webpack entry to support this new feature.
Changes
Path Configuration Updates (
paths.config.js
):blocksStyles
.Webpack Entry Updates (
entry.js
):loadBlockSpecificStyles
to conditionally load CSS files specific to blocks.assets/css/blocks
directory.Default Configuration Update (
config.js
):loadBlockSpecificStyles
option to the default configuration, with a default value set tofalse
.Requires this to be deployed to Scaffold: 10up/wp-scaffold#229
Checklist: