@plumeria/codemod 19.0.0 → 19.1.1

package/README.md

@@ -259,10 +259,10 @@ together with every file whose definitions they still need. A target
 overwritten.
 
 The export removes the `@plumeria/core` import, so a reference to `Style`,
-`StyleProps`, `WithoutProperties`, `StaticStyles` or `AtomicClassNameFor` is left
-without the import that declares it. Those are reported as
-`style-type-reference`, whether the type names a component prop, a type alias or
-a variable annotation.
+`StyleProps`, `WithoutProperties`, `StaticStyles`, `AtomicStyle`,
+`AtomicDynamicStyle` or `AtomicClassNameFor` is left without the import that
+declares it. Those are reported as `style-type-reference`, whether the type
+names a component prop, a type alias or a variable annotation.
 
 A module that declares nothing but style prop types is the one shape this does
 not reach: it defines no styles, so there is no stylesheet for the report to hold

package/dist/release.js

@@ -83,6 +83,8 @@ const STYLE_TYPES = new Set([
     'StyleProps',
     'WithoutProperties',
     'StaticStyles',
+    'AtomicStyle',
+    'AtomicDynamicStyle',
     'AtomicClassNameFor',
 ]);
 const memberOf = (node) => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@plumeria/codemod",
-  "version": "19.0.0",
+  "version": "19.1.1",
   "description": "Codemods for Plumeria: migrate a CSS Modules codebase in, export it back out, and rename the styling prop",
   "author": "Refirst 11",
   "license": "MIT",