Upgrade to postcss 6.x #374
Comments
|
"dependencies": {
|
|
Thanks for this issue. Feel free to make PR whenever you can (lot of work, I know). |
|
"postcss-font-family-system-ui": "^2.0.0" Edit: Just published ^2.0.1 that drops 0.12 support completely. Thanks to kind reminder from @Semigradsky. |
|
I've released https://github.com/postcss/postcss-calc/releases/tag/v6.0.0. |
|
I released https://github.com/jonathantneal/postcss-nesting which is now using v6 |
|
@Semigradsky, I have PRs for updating postcss-color-rebeccapurple. postcss/postcss-color-rebeccapurple#9 — updates PostCSS to v6, updates linters to support Node v4 syntax and then uses that syntax, improves the plugin to not partially update invalid colors (like "oldrebeccapurple"). postcss/postcss-color-rebeccapurple#8 — just updates PostCSS to v6. I made them separate PRs incase @MoOx had no interest in the other improvements at this time (or if he found them not to be suitable improvements). |
|
@Semigradsky, https://github.com/jonathantneal/postcss-pseudo-class-any-link is also updated. |
|
@Semigradsky, PRs submitted for |
|
@jonathantneal @Semigradsky I created a cssnext team in postcss org and you have been added as collab there. Will add you as collab on npm on each repo I have the rights on. |
|
My workflow is: commits + a "x.y.z" commit with changelog notes + package.json version bump + "npm run release" (see scripts ;)). You are the bosses here :) |
|
My recommendation will be to move to a monorepo for the repos we can + remove jscs and all outdated stuff in favor of eslint + eslint-config-i-am-meticulous + prettier + jest (with snapshots) but that might take some time :D |
|
High priority |
|
There's ways of expressing that sentiment that aren't condescending & rude, please show some respect for those of us who work on this stuff in our spare time. |
|
@ben-eb 😟 That wasn't meant to be consdescending or rude, I also asked how to help getting the last bits done 😕 |
|
@michael-ciniawsky, @Semigradsky, please review #384 |
1.2.0 - 2017-05-22 ------------------------------------------------ * Adds `npm run build-browser-only` option, which creates `index.html` alongside regular JS and CSS browser bundling. Useful for static hosts or via a BYO web server. * Adds provisional `postcss.config.js`, for upcoming PostCSS v6.0 (note: not implemented yet; CSSNext currently awaiting MoOx/postcss-cssnext#374) * Fixes PostCSS source maps in development * Adds `HOST` environment var for overriding `localhost` default * Adds `Running on http://localhost:4000/` default message when server starts (or whatever the correct `HOST` and `PORT` are) * Bumps NPM packages: "cross-env": "^5.0.0", "css-loader": "^0.28.1", "eslint-config-airbnb": "^15.0.0", "eslint-plugin-jsx-a11y": "^5.0.1", "eslint-plugin-react": "^7.0.1", "image-webpack-loader": "^3.3.1", "node-noop": "^1.0.0", "postcss-cssnext": "2.11.0", "postcss-loader": "^2.0.5", "postcss-nested": "^2.0.2", "promise-monofill": "^1.0.1", "sass-loader": "^6.0.5", "style-loader": "^0.18.0", "webpack": "^2.5.1", "webpack-bundle-analyzer": "^2.8.1", "webpack-dev-server": "^2.4.5", "webpack-node-externals": "^1.6.0" * Bumps `yarn.lock` * Merges #25 - .editorconfig ESLint fix eol-last
|
Hi! Seems that last deps is merged MattDiMu/postcss-replace-overflow-wrap#5 and new version have been released ( Could you release new cssnext version? |
|
What is missing here? Any plugin still needs update? |
|
For now, I can’t keep up. One of this can be merged and we can work from there, or it will be easier for me to release a different plugin with stages like babel. |
|
Any update on this issue ? |
|
Any sense update to chalk 2? And yes, any 🆙 ? |
|
@jonathantneal cant we ship a thing until a new solution that include stages is ready? |
|
Closing in favor of #400 |
This requires a major version bump.
PostCSS Changelog
The text was updated successfully, but these errors were encountered: