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.
There is some confusion about the warning that is shown from the Browserslist dependency in the tailwind CLI. See here and here for examples of such confusion.
The warning appears once the Browserslist package is more than six months old. The warning is particularly confusing because it proposes to run an npx command to resolve the issue. Because this is a packaged dependency of the tailwind CLI, this makes no sense. Ideally this would be fixed upstream (I personally think it's not a good idea to print such warnings in the first place), but I don't know how to go about that. See these issues for more background on this potential can of worms. This is an attempt to silence the warning for this particular use-case, which admittedly is less ideal, but gets the job done.
By setting the environment variable
BROWSERSLIST_IGNORE_OLD_DATA
, the warning about an outdated browserslist can be silenced.The original warning for completeness:
This features is not documented in the browserslist project. It's implemented here.
--
Just as an aside: the same can be accomplished without any changes to this package, in user-config only. One can put this in
config.exs
instead:This has the same effect as it sets the same environment variable from the client config. It uses the
:env
config key (which is currently not documented).