Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Discussion options

The most recent version of postcss-preset-env doesn’t have the most up-to-date version of browserslist, so is there a way to make postcss-preset-env detect a separate browserslist installation and rely on its data, instead of the browserslist dependency within postcss-preset-env?

You must be logged in to vote

Hey @brycewray thats a great question!

Because of how npm works and how we’ve specified the dependencies, npm will actually install the latest version in range. This means that any version after ours that isn’t breaking is a valid version and will just work/be installed in a normal installation

Replies: 1 comment · 1 reply

Comment options

Hey @brycewray thats a great question!

Because of how npm works and how we’ve specified the dependencies, npm will actually install the latest version in range. This means that any version after ours that isn’t breaking is a valid version and will just work/be installed in a normal installation

You must be logged in to vote
1 reply
@brycewray
Comment options

@Antonio-Laguna Thanks! Very helpful info. Tried in vain to find it through searching — well, everywhere — and had no luck.

Answer selected by brycewray
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
🙏
Q&A
Labels
None yet
2 participants
Morty Proxy This is a proxified and sanitized view of the page, visit original site.