-
Notifications
You must be signed in to change notification settings - Fork 331
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
Upgrade to postcss version 8 is blocked on oldie #2469
Comments
I did a little investigation and tried to understand what effect each of the transformations built into I disabled each plugin in turn, re-compiled the dist folder and compared the outputted CSS to a version generated with the current plugin config. Salvage :nth-child (
|
As we're now planning to drop IE8 in v5 of Frontend, we will likely be dropping oldie entirely. Should we consider upgrading PostCSS a task for v5? |
YES!! 😄 |
As discussed in #2469 we’ve dropped various unused or unnecessary plugins This includes `:not` removal as rulesets without selectors were left behind
As discussed in #2469 we’ve dropped various unused or unnecessary plugins This includes `:not` removal as rulesets without selectors were left behind
As discussed in #2469 we’ve dropped various unused or unnecessary plugins This includes `:not` removal as rulesets without selectors were left behind
As discussed in #2469 we’ve dropped various unused or unnecessary plugins This includes `:not` removal as rulesets without selectors were left behind
As discussed in #2469 we’ve dropped various unused or unnecessary plugins This includes `:not` removal as rulesets without selectors were left behind
As discussed in #2469 we’ve dropped various unused or unnecessary plugins This includes `:not` removal as rulesets without selectors were left behind
As discussed in #2469 we’ve dropped various unused or unnecessary plugins This includes `:not` removal as rulesets without selectors were left behind
As discussed in #2469 we’ve dropped various unused or unnecessary plugins This includes `:not` removal as rulesets without selectors were left behind
As discussed in #2469 we’ve dropped various unused or unnecessary plugins This includes `:not` removal as rulesets without selectors were left behind
As discussed in #2469 we’ve dropped various unused or unnecessary plugins This includes `:not` removal as rulesets without selectors were left behind
As discussed in #2469 we’ve dropped various unused or unnecessary plugins This includes `:not` removal as rulesets without selectors were left behind
As discussed in #2469 we’ve dropped various unused or unnecessary plugins This includes `:not` removal as rulesets without selectors were left behind
As discussed in #2469 we’ve dropped various unused or unnecessary plugins This includes `:not` removal as rulesets without selectors were left behind
Looks like we can close this one as we're using Gathered some usage information in this comment #3001 (review) with some plugins using older So other problems still lurk. We saw these when considering
|
Cause
The package oldie was last published 6 years ago and does not appear to be maintained. It and its dependents require postcss version 5.
We currently use gulp-postcss for our Sass to minified CSS pipeline, which tries to arrange things so that the CSS is parsed only once, and so uses its own version of postcss to run any plugins.
When running
gulp scss:compile
with the latest version of gulp-postcss and postcss we get the following error:Consequences
We cannot upgrade to postcss 8 without finding a replacement for oldie. postcss 8 has a number of security fixes and advantages, including new best practice where plugins are asked to use it as a peer dependency rather than as a direct dependency, which results in a smaller dependency tree for us.
Impact of debt
Low
Reason (impact of debt)
No response
Effort to pay down
Medium
Reason (effort to pay down)
We could fork oldie, or use a vendored version, to get around the requirement for older dependencies. I think the code in oldie should still work, it's just tying a number of other plugins together.Looked into this, most of the dependencies for oldie are also unmaintained 😢.Overall rating
Low
Reason (overall rating)
No response
The text was updated successfully, but these errors were encountered: