@plumeria/codemod 21.0.0 → 21.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +2 -2
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -220,7 +220,7 @@ reported as `dynamic-style-access` and its definitions stay in Plumeria.
220
220
 
221
221
  ### Global styles
222
222
 
223
- `css.createTheme` and `css.viewTransition` produce rules that belong in a global
223
+ `css.createTheme` and `css.viewTransitionClass` produce rules that belong in a global
224
224
  stylesheet, not in a CSS Module. The codemod extracts them and appends them to
225
225
  the stylesheet the project already loads — `app/global.css` or
226
226
  `styles/global.css`, under `src` or not, spelled `global` or `globals` — and
@@ -228,7 +228,7 @@ writes `src/styles/global.css` (or `styles/global.css` when `src` does not
228
228
  exist) when it finds none. Theme tokens become CSS custom properties under
229
229
  `:where(:root)` and the theme selector; view transitions become
230
230
  `::view-transition-*` pseudo-element rules. References in style objects are
231
- replaced by their generated names. A `keyframes` or `viewTransition` nothing the
231
+ replaced by their generated names. A `keyframes` or `viewTransitionClass` nothing the
232
232
  migration exports reaches is left where it is.
233
233
 
234
234
  A CSS Module renames the value of `animation-name` the way it renames a class,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@plumeria/codemod",
3
- "version": "21.0.0",
3
+ "version": "21.1.0",
4
4
  "description": "Codemods for Plumeria: migrate a CSS Modules codebase in, export it back out, and rename the styling prop or an API",
5
5
  "author": "Refirst 11",
6
6
  "license": "MIT",