-
Notifications
You must be signed in to change notification settings - Fork 12k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updating autoprefixer to v7.1.x and postcss v6.0.x #7271
Comments
This is waiting on cssnano 4.0 to be released to have a full postcss 6 pipeline. |
Note that Autoprefixer 7 disables CSS Grid prefixes for IE by default so unless CLI passes the option explicitly (and unless there are more breaking changes there) the update to Autoprefixer 7 will be breaking and will require a major version bump of Angular CLI. |
@mgol I wonder if would be sufficient to simply set grid: true, if that will be enough to make it possible to move up to v7, without having to simultaneously solve the problem of making autoprefixer configurable. |
@kylecordes That might be worth it. From what I see in the changelog, this is the only breaking change aparts from dropping old Node versions that CLI doesn't support anyway. It'd still be worth it to be able to configure PostCSS plugins but that's a separate issue. |
@mgol I have a workaround in progress that does this and appears to work fine. Writeup coming soon. |
@mgol @kylecordes PRs are welcome for the autoprefixer upgrade. As mentioned |
These dependencies have been update |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bug Report or Feature Request (mark with an
x
)Versions.
@angular/[email protected]
Desired functionality.
In my project, i use css-grids and the default option in autoprefixer 6 is grid: true
In autoprefixer 7, it's grid: false
i think there is some other improvements
Mention any other details that might be useful.
The text was updated successfully, but these errors were encountered: