Skip to content
This repository was archived by the owner on Dec 19, 2024. It is now read-only.

Use PostCSS 6 and update all plugins #384

Closed
wants to merge 19 commits into from
Closed

Use PostCSS 6 and update all plugins #384

wants to merge 19 commits into from

Conversation

jonathantneal
Copy link
Collaborator

@jonathantneal jonathantneal commented May 17, 2017

This PR updates PostCSS to 6, and then updates all plugins to their latest versions.

Each test independently passes all tests. Most updates do not affect tests. All updates were purely whitespace changes except for nesting, which removes an otherwise empty parent rule which contains only nested rules. Any changes to tests are found in their corresponding commit.

Resolves #374

Copy link

@michael-ciniawsky michael-ciniawsky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The #375 comments maybe inappropiated for now (so feel free to ignore). It could be done in another semver major release anytime and PostCSS 6 compatibility is more urgent atm 😛. Thx very much for putting this together so quickly 🎉

@@ -98,8 +97,9 @@
"npmpub": "^3.1.0",
"object-assign": "^3.0.0",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since PostCSS 6 requires node >= 4 anyways, maybe time to get rid off that if it doesn't require to much changes 😛

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a devDep, so doesn't really need done, but it definitely could be done.

"postcss-browser-reporter": "^0.4.0",
"postcss-import": "^7.1.3",
"postcss-import": "^10.0.0",
"postcss-loader": "^0.8.0",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bump to v2.0.5 aswell ? 🙃

"postcss-color-function": "^2.0.0",
"postcss-color-gray": "^3.0.0",
"postcss-color-hex-alpha": "^2.0.0",
"pleeease-filters": "^4.0.0",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#375 ?

package.json Outdated
"postcss-custom-selectors": "^3.0.0",
"postcss-font-family-system-ui": "^1.0.1",
"postcss-font-variant": "^2.0.0",
"postcss-color-rgba-fallback": "^2.2.0",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#375 ?

package.json Outdated
"autoprefixer": "^6.0.2",
"caniuse-api": "^1.5.3",
"autoprefixer": "^7.1.0",
"caniuse-api": "^2.0.0",
"chalk": "^1.1.1",
"pixrem": "^3.0.0",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#375 ?

package.json Outdated
"postcss-media-minmax": "^3.0.0",
"postcss-nesting": "^3.0.0",
"postcss-pseudo-class-any-link": "^4.0.0",
"postcss-pseudoelements": "^4.0.0",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#375 ?

@michael-ciniawsky
Copy link

Travis fails because of node v0.12, better remove it from travis.yml ? 🙃

@jonathantneal
Copy link
Collaborator Author

Thank you for your patience. I love my company, so that always comes first! :D

@michael-ciniawsky, great catch, updated.

As for #375, I think we should merge this in before the PR becomes too big. I will make a separate PR for that.

@jonathantneal
Copy link
Collaborator Author

jonathantneal commented May 17, 2017

@michael-ciniawsky, @RyanZim, do not be fooled by the red X, the tests should have passed. 😄

It looks like the last test failed to initialize; see: https://ci.appveyor.com/project/MoOx/postcss-cssnext/build/85/job/0iinwm41xjcwjftk

Could someone re-run it?

@Semigradsky
Copy link
Collaborator

Hi @jonathantneal! Could you change base to 3.0 branch?

@jonathantneal jonathantneal changed the base branch from master to 3.0 May 18, 2017 13:04
- Updates tests for whitespacing, which PostCSS 6 captures more
accurately.
No test changes required
One test is changed because `@apply` changes how nested spacing is
handled.
No test changes required
No test changes needed
No text changes needed
No test changes needed
To test changes needed
No test changes needed
One test changes, as an rgb rebeccapurple compiles to a shorter hex
version
No test changes needed
No test changes needed
No test changes needed
No test changes needed
Nesting 3 removes unnecessary parents and normalizes spacing (similar
to the new apply)
No testing changes needed
No testing changes needed
No testing changes needed
@jonathantneal
Copy link
Collaborator Author

@Semigradsky, yes, I have rebased against 3.0 and updated the base of this PR.

@jonathantneal
Copy link
Collaborator Author

@Semigradsky, ping?

@jonathantneal
Copy link
Collaborator Author

With these approved, once these are in, we can pull in any additional plugin updates that have come in since this was opened.

@Semigradsky
Copy link
Collaborator

Semigradsky commented May 25, 2017

I see that there are two problems left that prevent us from releasing a new version.

  1. The future of nesting and @apply. We will remove them from the new version? I did not see the final decision. ping @MoOx

  2. The future of unmaintained plugins. We send PR but no any reaction. ping @MattDiMu
    We can forked these repositories and publish to npm for new names.

@jonathantneal
Copy link
Collaborator Author

jonathantneal commented May 25, 2017

@Semigradsky, I think starting with getting this in is a big first step. Then...

  1. CSS @apply is actively abandoned/disliked by the creator and should be removed. Citation from author: http://www.xanthir.com/b4o00

  2. CSS Nesting is merely in the backlog, along with a handful of other specs; lacking the interest/focus to move them ahead. It should remain. Citation from author: https://twitter.com/tabatkins/status/862409545489895424

@dmarchena
Copy link
Contributor

Sorry @Semigradsky, I didn't see your PRs. I've just accepted them and published new versions for postcss-color-rgb and postcss-color-hsl.

@jonathantneal
Copy link
Collaborator Author

cssnext is now so out of date, I am just using a local package, because I otherwise deal with a lot of bugs that people think means the plugins are still broken. For those who need this, it’s:

require('postcss-custom-properties')(),
require('postcss-apply')(),
require('postcss-image-set-polyfill')(),
require('postcss-nesting')(),
require('postcss-custom-media')(),
require('postcss-media-minmax')(),
require('postcss-custom-selectors')(),
require('postcss-attribute-case-insensitive')(),
require('postcss-color-rebeccapurple')(),
require('postcss-color-hwb')(),
require('postcss-color-hsl')(),
require('postcss-color-rgb')(),
require('postcss-color-gray')(),
require('postcss-color-hex-alpha')(),
require('postcss-color-function')(),
require('postcss-font-family-system-ui')(),
require('postcss-font-variant')(),
require('postcss-initial')(),
require('postcss-selector-matches')(),
require('postcss-selector-not')(),
require('postcss-pseudo-class-any-link')(),
require('postcss-replace-overflow-wrap')(),

All of these aforementioned plugins are now working with PostCSS 6x.

@francoisromain
Copy link

@jonathantneal just to understand, could you list what is out of date in cssnext, please?

@Semigradsky
Copy link
Collaborator

@jonathantneal could you update dependencies and remove @apply?
I see that this is all that remains to be done before the merge.

@jonathantneal
Copy link
Collaborator Author

@Semigradsky, it would be easier to redo this in #385

Are we removing the non-future plugins? Or are they already gone?

@Semigradsky
Copy link
Collaborator

it would be easier to redo this in #385

No problem. Then it remains only to update the plugins.
postcss-color-hsl, postcss-replace-overflow-wrap, etc.

@Semigradsky Semigradsky mentioned this pull request Jun 3, 2017
@doochik
Copy link

doochik commented Jun 5, 2017

All plugins are released. Can you update PR?

"postcss-pseudo-class-any-link": "^1.0.0",
"postcss-initial": "^2.0.0",
"postcss-media-minmax": "^3.0.0",
"postcss-nesting": "^3.0.0",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The most recent version of postcss-nesting is 4.0.1

Copy link

@Kurre Kurre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Quickly reviewed all dependencies and commented on those which should/could be bumbed up.

It seems that only outdated package is postcss-browser-reporter (if I didn't miss anything).

Hopefully this helps maintainers a bit :)

"postcss-calc": "^6.0.0",
"postcss-color-function": "^4.0.0",
"postcss-color-gray": "^4.0.0",
"postcss-color-hex-alpha": "^3.0.0",
"postcss-color-hsl": "^1.0.5",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PostCSS v6 support with ^2.0.0

"postcss-color-hwb": "^2.0.0",
"postcss-color-rebeccapurple": "^2.0.0",
"postcss-color-hwb": "^3.0.0",
"postcss-color-rebeccapurple": "^3.0.0",
"postcss-color-rgb": "^1.1.4",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PostCSS v6 support with ^2.0.0

"postcss-custom-properties": "^6.0.1",
"postcss-custom-selectors": "^4.0.1",
"postcss-font-family-system-ui": "^2.0.1",
"postcss-font-variant": "^3.0.0",
"postcss-image-set-polyfill": "^0.3.3",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PostCSS v6 support with ^0.3.5

"postcss-initial": "^2.0.0",
"postcss-media-minmax": "^3.0.0",
"postcss-nesting": "^3.0.0",
"postcss-pseudo-class-any-link": "^4.0.0",
"postcss-replace-overflow-wrap": "^1.0.0",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PostCSS v6 support with ^2.0.0

@@ -95,8 +94,9 @@
"npmpub": "^3.1.0",
"object-assign": "^3.0.0",
"opn": "^1.0.2",
"postcss-apply": "^0.7.0",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can be bumbed to ^0.8.0

@@ -95,8 +94,9 @@
"npmpub": "^3.1.0",
"object-assign": "^3.0.0",
"opn": "^1.0.2",
"postcss-apply": "^0.7.0",
"postcss-browser-reporter": "^0.4.0",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing PostCSS v6 support

"postcss-browser-reporter": "^0.4.0",
"postcss-import": "^7.1.3",
"postcss-import": "^10.0.0",
"postcss-loader": "^0.8.0",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PostCSS v6 support with ^2.0.5

"postcss-browser-reporter": "^0.4.0",
"postcss-import": "^7.1.3",
"postcss-import": "^10.0.0",
"postcss-loader": "^0.8.0",
"postcss-reporter": "^1.3.0",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PostCSS v6 support with ^4.0.0

"postcss-browser-reporter": "^0.4.0",
"postcss-import": "^7.1.3",
"postcss-import": "^10.0.0",
"postcss-loader": "^0.8.0",
"postcss-reporter": "^1.3.0",
"postcss-url": "^5.0.2",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PostCSS v6 support with ^7.0.0

@longlho
Copy link

longlho commented Jun 26, 2017

hi guys, any progress on this?

@shouze
Copy link

shouze commented Jun 28, 2017

@jonathantneal do you have some time to integrate @Kurre & @jaap3 feedbacks? So close to merge as appveyor failure looks like a false positive.

@jonathantneal
Copy link
Collaborator Author

I don’t. This should have been merged when it was relevant.

@MoOx
Copy link
Owner

MoOx commented Jul 3, 2017

Why is this not remevant anymore?

@shouze
Copy link

shouze commented Jul 3, 2017

Yes, I also want to know why (because I've asked Norah Jones and she don't know why 🎵 )

@MoOx
Copy link
Owner

MoOx commented Jul 3, 2017 via email

@shouze
Copy link

shouze commented Jul 3, 2017

@MoOx would you mind if I reopen this PR & adapt last things to get it merged ASAP?

@longlho
Copy link

longlho commented Jul 3, 2017

@shouze I opened another one #398

@MoOx
Copy link
Owner

MoOx commented Jul 3, 2017 via email

@MoOx MoOx mentioned this pull request Jul 4, 2017
@MoOx
Copy link
Owner

MoOx commented Jul 4, 2017

See #400 for current WIP.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.