search

plotly / react-chart-editor

Customizable React-based editor panel for Plotly charts
https://plotly.github.io/react-chart-editor/
MIT License
499 stars 101 forks source link

Update dependency postcss to v8 #1075

Closed renovate[bot] closed 3 years ago

renovate[bot] commented 3 years ago

This PR contains the following updates:

Package Type Update Change
postcss (source) devDependencies major 7.0.34 -> 8.0.5

Release Notes

postcss/postcss ### [`v8.0.5`](https://togithub.com/postcss/postcss/blob/master/CHANGELOG.md#​805) [Compare Source](https://togithub.com/postcss/postcss/compare/8.0.4...8.0.5) - Update changelog. ### [`v8.0.4`](https://togithub.com/postcss/postcss/blob/master/CHANGELOG.md#​804) [Compare Source](https://togithub.com/postcss/postcss/compare/8.0.3...8.0.4) - Fixed `Cannot read property 'line' of null` error. - Fixed source map support for declarations. ### [`v8.0.3`](https://togithub.com/postcss/postcss/blob/master/CHANGELOG.md#​803) [Compare Source](https://togithub.com/postcss/postcss/compare/8.0.2...8.0.3) - Fixed client-side bundling support. ### [`v8.0.2`](https://togithub.com/postcss/postcss/blob/master/CHANGELOG.md#​802) [Compare Source](https://togithub.com/postcss/postcss/compare/8.0.1...8.0.2) - Fixed plugin packs support. ### [`v8.0.1`](https://togithub.com/postcss/postcss/blob/master/CHANGELOG.md#​801) [Compare Source](https://togithub.com/postcss/postcss/compare/8.0.0...8.0.1) - Updated `Processor#version`. ### [`v8.0.0`](https://togithub.com/postcss/postcss/releases/8.0.0) [Compare Source](https://togithub.com/postcss/postcss/compare/7.0.34...8.0.0) President Ose seal PostCSS 8.0 brings new plugin API, `node_modules` size reduction, better source map support, and CSS parser improvements. Check out [a day-by-day diary](https://twitter.com/PostCSS/status/1273368785592999936) of PostCSS 8.0 development process. #### Known Issues - `postcss-cli` need to be updated PostCSS to run new plugins - `gulp-postcss` need to be updated PostCSS to run new plugins - `postcss-load-plugins` (used by some environments) can’t load new plugins #### Thanks to Sponsors With more than [100 M downloads per month](https://npm-stat.com/charts.html?package=postcss), it becomes hard to support PostCSS in free time. For instance, getting the 8.0 release ready took [4 months of work](https://twitter.com/PostCSS/status/1273368785592999936). This release was possible thanks to out community. [**Tailwind CSS**](https://tailwindcss.com/), [**De Voorhoede**](https://www.voorhoede.nl/en/), [**InVision AG**](https://www.ivx.com/), [**Brainbow**](https://opencollective.com/brnbw), and [many individual contributions](https://opencollective.com/postcss#section-contributors). Sponsored by Tailwind CSS If your company wants to support the sustainability of front-end infrastructure or just wants to give some love to PostCSS, you can join our supporters by: - [**Tidelift**](https://tidelift.com/) with a Spotify-like subscription model and supporting all projects from your lock file. - Direct donations in [**PostCSS & Autoprefixer Open Collective**](https://opencollective.com/postcss#section-contributors). #### Breaking Changes We try to avoid any breaking changes for end-users: - PostCSS 8 dropped **Node.js 6.x, 8.x, 11.x, and 13.x** versions support. All these versions have no security updates anymore. - We now serve ES6+ sources in the npm package **without Babel** compilation. If you are creating tools like CodePen and put PostCSS into the client-side JS bundle, you may need to run Babel on `node_modules/postcss` for old browsers. - We removed rarely used `postcss.vendor` API. #### New Plugin API The biggest change in PostCSS 8 is a new plugin API. Thanks to [@​BondarenkoAlex](https://togithub.com/BondarenkoAlex) for big help in creating a new API. ```js module.exports = () => { return { postcssPlugin: 'postcss-will-change', Declaration: { 'will-change': (decl, { Declaration }) => { decl.cloneBefore( new Declaration({ prop: 'backface-visibility', value: 'hidden' }) ) } } } } module.exports.postcss = true ``` We know that rewriting old plugins will take time, but the new API will improve the end-user’s experience and make life easier for plugin developers: - With new API, all plugins can share a single scan of the CSS tree. It makes CSS processing up to **20% faster**. - Because npm often duplicates dependencies, you may have many `postcss` duplicates in your `node_modules`. New API fixes this problem. - Plugins will re-visit changed nodes to **reduce compatibility issues** between plugins. Now the order of plugins in your PostCSS config will be less important. - New API is close to Babel’s visitor API. These resources will help plugin developers in API migration: - [**The Migration Guide**](https://evilmartians.com/chronicles/postcss-8-plugin-migration) - [**Writing a PostCSS Plugin**](https://togithub.com/postcss/postcss/blob/master/docs/writing-a-plugin.md) - We have a [**Gitter chat**](https://gitter.im/postcss/postcss) open for all questions related to plugin migration. PostCSS development guidelines were also changed: - Now it is prohibited to create own AST on top of PostCSS AST classes since it could lead to [painful bugs](https://togithub.com/postcss/postcss/issues/1305) due to the usage private APIs. - Plugins and runners must have `postcss` in `peerDependencies`. #### New Website without React Previously PostCSS used [a React-based framework](https://togithub.com/phenomic/phenomic) for the project's website. Since we have a static website, we decided to migrate to a React-free framework and got good performance improvements: - **360 → 20** ms for Max Potential First Input Delay - **3.3 → 1.5** seconds for First CPU Idle - **3.3 → 1.5** seconds for Time to Interactive Check out [**postcss.org**](https://postcss.org/) and [**new API docs**](https://postcss.org/api/) that feature the awesome alchemy-inspired design by [@​okonet](https://togithub.com/okonet). PostCSS website performance results We also removed Google Analytics tracking scripts and encourage other open source projects to be an example in caring about user’s privacy and performance. #### Parser Improvments Did you know that all examples below are valid CSS? ```css :root { --empty: ; --JSON: [1, "2", {"three": {"a":1}}, [4]]; --javascript: function(rule) { console.log(rule) }; } @​supports (--element(".minwidth", { "minWidth": 300 })) { [--self] { background: greenyellow; } } ``` Now PostCSS parses even those rare edge cases correctly. Thanks to Tailwind CSS and Prettier teams for adding more cases to our [CSS parser tests collection](https://togithub.com/postcss/postcss-parser-tests/). Note that now `--roundMixin: { border-radius: 8px }` will be parsed as a `Declaration` with the `{ border-radius: 8px }` value. #### Better Source Map Support We have added support for two new source map formats: [**Index map**](https://sourcemaps.info/spec.html#h.535es3xeprgt) and [**JSON**](https://togithub.com/postcss/postcss/issues/1371) (`data:application/json`). PostCSS 8 is now much closer to the source map spec. Thanks to the Google team for reports: - We now [treat](https://togithub.com/postcss/postcss/issues/1347) `sources` in map **as URLs** instead of file paths. - We now [resolve](https://togithub.com/postcss/postcss/issues/1348) `sources` **relative to map file**, not CSS file. A few source map APIs were added: - `opts.maps.absolute = true` option for [absolute paths](https://togithub.com/postcss/postcss/issues/1352) in source map. - `opts.maps.annotation = (file, root) => url` for a [dynamic path](https://togithub.com/postcss/postcss/issues/1324) to source map. - `Node#origin()` now returns `position.url` in addition to `position.file` for compatibility with absolute URLs in source map’s `sources`. #### API Changes We have added **ES modules** support and now we **export all classes** from the main entry: ```js import { CssSyntaxError, parse } from "postcss" ``` [@​graberzz](https://togithub.com/graberzz) added [`Node#source.offset`](https://togithub.com/postcss/postcss/issues/1325) in addition to `line` and `column`. CSS Custom Properties and Sass-like `$`-variables now have a special `Declaration#variable` mark: ```js const root = parse(` :root { --propery: value; } $variable: value `) root.first.first.variable //=> true root.last.variable //=> true ``` #### TypeScript PostCSS now has a first-class TypeScript support: - We moved API docs from JSDoc to [**TypeDoc**](https://typedoc.org/). Check out our [**new API docs**](https://postcss.org/api/). - We are using [**check-dts**](https://togithub.com/ai/check-dts) to test types with [special unit tests](https://togithub.com/postcss/postcss/blob/master/test/errors.ts). - We keep types in separate files for better readability. - With the new structure and test system, we fixed many small issues in types. #### Other Changes - [Fixed calling `replaceWith`](https://togithub.com/postcss/postcss/pull/1368) with input replaced node (by [@​josephkaptur](https://togithub.com/josephkaptur)). - Reduce dependencies by replacing `chalk` to [`colorette`](https://togithub.com/jorgebucaran/colorette). - Added `Declaration#value` [auto-conversion](https://togithub.com/postcss/postcss/issues/1373) to string to prevent plugin’s bugs. - Fixed building PostCSS with Rollup (by [@​MapGrid](https://togithub.com/MapGrid)) because of [circular dependencies](https://togithub.com/postcss/postcss/pull/1321). - Moved unknown source from counter to random IDs: `:10:6`. - Removed docs from the npm package.

Renovate configuration

:date: Schedule: At any time (no schedule defined).

:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.

:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

This PR has been generated by WhiteSource Renovate. View repository job log here.