Skip to content

Conversation

@moonglum
Copy link
Member

@moonglum moonglum commented Nov 2, 2025

This is a breaking change, as browsers will no longer be passed to the plugins, which moves the responsibility for determining the correct browserslist to the plugin.

This is a breaking change, as browsers will no longer be passed to the
plugins, which moves the responsibility for determining the correct
browserslist to the plugin.
@FND
Copy link
Contributor

FND commented Nov 3, 2025

I'm a little uncertain about the implications of this: I vaguely remember us talking about plugins (e.g. faucet-js and faucet-css) having independent browserslist instances/configuration or at least doing redundant discovery. Is that a concern worth exploring?

PS: This kinda renders 2a19f94 moot; we should probably drop that commit and raise the Node version elsewhere.

@moonglum moonglum changed the base branch from main-revised to main November 3, 2025 12:15
@moonglum
Copy link
Member Author

moonglum commented Nov 3, 2025

Yes, this is the most "controversial" of the PRs. Back in April, I created the PR for the change for faucet-pipeline-sass. We would need a similar PR for faucet-pipeline-js and faucet-pipeline-css.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants