Move postcss-prefix-custom-properties from peerDependencies to devDependencies#42592
Merged
mdo merged 1 commit intoJun 28, 2026
Conversation
mdo
deleted the
v6-dev-jd-move-postcss-prefix-custom-properties-to-dev-dependencies
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
postcss-prefix-custom-propertiesis currently listed as a peer dependency, but it is used as part of Bootstrap's internal build process to generate the final CSS output.Some users who build Bootstrap from the Sass source with their own custom toolchain may rely on this PostCSS step, but this is not the default usage pattern. Most users consume Bootstrap's prebuilt CSS, where this transformation has already been applied.
Moving it to
devDependencieskeeps ownership of this build step within Bootstrap while still allowing advanced users with custom build pipelines to explicitly include the plugin when needed. On top of that, we don't force the use of PostCSS by adding it to peer dependencies.This does not change the generated CSS or the Sass customization workflow; it only updates the dependency declaration to better reflect how the package is consumed.