@sproutsocial/racine 31.7.14 → 31.7.16

package/CHANGELOG.md

@@ -1,5 +1,34 @@
 # Change Log
 
+## 31.7.16
+
+### Patch Changes
+
+- Updated dependencies [487cab4]
+- Updated dependencies [f3bed6c]
+- Updated dependencies [50982e3]
+  - @sproutsocial/seeds-react-panel@1.1.0
+  - @sproutsocial/seeds-react-peek-in@0.4.0
+  - @sproutsocial/seeds-react-table@1.0.51
+  - @sproutsocial/seeds-react-data-table@2.6.33
+
+## 31.7.15
+
+### Patch Changes
+
+- Updated dependencies [a0b98f1]
+- Updated dependencies [ea120a6]
+- Updated dependencies [690479a]
+- Updated dependencies [c36361c]
+- Updated dependencies [a635951]
+  - @sproutsocial/seeds-react-character-counter@1.0.8
+  - @sproutsocial/seeds-react-grid@0.2.13
+  - @sproutsocial/seeds-react-duration@1.0.32
+  - @sproutsocial/seeds-react-image@1.0.29
+  - @sproutsocial/seeds-react-empty-state@1.0.31
+  - @sproutsocial/seeds-react-avatar@1.1.25
+  - @sproutsocial/seeds-react-message@1.0.59
+
 ## 31.7.14
 
 ### Patch Changes

package/README.NPM.md

@@ -7,4 +7,4 @@
   <a href="https://github.com/sproutsocial/seeds/blob/main/seeds-react/racine/LICENSE"><img src="https://flat.badgen.net/badge/license/MIT/blue" alt=""></a>
 </p>
 
-Racine!
+Racine!

package/README.md

@@ -88,6 +88,7 @@ Racine's file structure is set up like this:
   - `ComponentName` - Deprecated components that won't get added to the monorepo have a folder within the `src` directory.
 
 Most components in Racine are exported at the root from their own packages. Each package typically structures its files similarly to how they appeared in Racine:
+
 - `src`
   - `index.js` - This file should contain all necessary exports for the component.
   - `index.stories.js` - Storybook stories can be written here.
@@ -108,26 +109,31 @@ And you can interact with Racine via the command line with these commands:
 Codemods are automated scripts that help migrate code when component APIs change. They're available via the `racine-codemod` CLI tool and are automatically discovered from both racine and other `@sproutsocial/seeds-react-*` packages.
 
 **List available codemods:**
+
 ```bash
 racine-codemod
 ```
 
 **View codemod documentation:**
+
 ```bash
 racine-codemod <codemod-name>
 ```
 
 **Run a codemod:**
+
 ```bash
 racine-codemod <codemod-name> <path-to-files>
 ```
 
 **Example:**
+
 ```bash
 racine-codemod badge-1.x-to-2.x src --parser=tsx --quote=double
 ```
 
 After running a codemod, you should run Prettier to fix any formatting issues:
+
 ```bash
 yarn format
 ```
@@ -182,6 +188,7 @@ Racine components are documented in [Seeds](https://sproutsocial.com/seeds/compo
 When making breaking changes to a component API, you should create a codemod to help users migrate their code. Codemods should be added to the package that needs migration (not racine), and will be automatically discovered by the `racine-codemod` CLI.
 
 **When to create a codemod:**
+
 - Removing or renaming props
 - Changing prop types or values
 - Breaking API changes that affect multiple files
@@ -189,22 +196,28 @@ When making breaking changes to a component API, you should create a codemod to
 **Initial Setup** (for packages adding their first codemod):
 
 1. **Update `tsup.config.ts`**:
+
    - Add a separate config entry for codemods:
+
    ```typescript
    export default defineConfig([
      // Main package build
-     { entry: ["src/index.ts"], format: ["cjs", "esm"], /* ... */ },
+     { entry: ["src/index.ts"], format: ["cjs", "esm"] /* ... */ },
      // Codemods build (CJS only)
-     { entry: ["codemods/**/*.ts"], format: ["cjs"], dts: false, /* ... */ },
+     { entry: ["codemods/**/*.ts"], format: ["cjs"], dts: false /* ... */ },
    ]);
    ```
 
 2. **Update `package.json`**:
+
    - Add `exports` field for codemods:
+
    ```json
    {
      "exports": {
-       ".": { /* existing exports */ },
+       ".": {
+         /* existing exports */
+       },
        "./codemods/*": {
          "require": "./dist/codemods/*.js"
        }
@@ -212,6 +225,7 @@ When making breaking changes to a component API, you should create a codemod to
      "files": ["dist", "codemods"]
    }
    ```
+
    - Add `@types/jscodeshift` and `jscodeshift` to devDependencies (if not already present)
 
 3. **Update `tsconfig.json`**:
@@ -228,11 +242,13 @@ When making breaking changes to a component API, you should create a codemod to
 7. Codemod will be discoverable via `racine-codemod` CLI after package is built
 
 **Testing codemods locally:**
+
 - Run `yarn build` to compile codemod to JavaScript
 - Run `yarn test` to run codemod tests
 - Test codemod execution: `racine-codemod my-codemod path/to/test/files`
 
 **Example structure:**
+
 ```
 my-package/
   codemods/