You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if you supply an invalid browser string to Autoprefixer, the tool fails with the message: internal error.
This is not helpful at all. Several of my customers have wasted quite a lot of time trying to figure out why Autoprefixer won't run, only to discover that they made a typo in the browser string parameter.
It would be very useful to provide a descriptive error message in this case. Something like: "Autoprefixer failed to run because the supplied browser string parameter is not valid: [browser string parameter]"
The text was updated successfully, but these errors were encountered:
What would be really cool is to add a function to the CLI that lets you pass a proposed browser string to Autoprefixer and have the tool return whether or not that string is valid. This would let me validate browser strings as soon as the user enters them rather than waiting until AP runs and fails.
Currently, if you supply an invalid browser string to Autoprefixer, the tool fails with the message:
internal error
.This is not helpful at all. Several of my customers have wasted quite a lot of time trying to figure out why Autoprefixer won't run, only to discover that they made a typo in the browser string parameter.
It would be very useful to provide a descriptive error message in this case. Something like: "Autoprefixer failed to run because the supplied browser string parameter is not valid: [browser string parameter]"
The text was updated successfully, but these errors were encountered: