Devendra174's picture
Upload folder using huggingface_hub
1e92f2d verified

@chakra-ui/cli

3.23.0

3.22.0

3.21.1

Patch Changes

  • 517ba37 Thanks @segunadebayo! - Fix issue where typegen command fails silently with misleading console output when prettier exits with a formatting error

3.21.0

3.20.0

3.19.2

Patch Changes

  • #10059 a289c3c Thanks @isBatak! - - System: add explicit undefined to generated types to support TS exactOptionalPropertyTypes

3.19.1

3.19.0

3.18.0

3.17.0

3.16.1

3.16.0

3.15.1

Patch Changes

3.15.0

3.14.2

3.14.1

3.14.0

3.13.0

3.12.0

3.11.0

3.10.0

3.9.0

3.8.2

3.8.1

3.8.0

3.7.0

3.6.0

Patch Changes

  • 07f2c56 Thanks @segunadebayo! - Fix issue where CLI doesn't properly check for existing files when adding snippets.

3.5.1

3.5.0

3.4.0

3.3.3

3.3.2

3.3.1

3.3.0

Minor Changes

  • e5ecd91 Thanks @segunadebayo! - Add support for --tsx flag in the snippet add command to allow explicitly specifying tsx/jsx file generation.

3.2.5

3.2.4

3.2.3

3.2.2

Patch Changes

3.2.1

Patch Changes

  • c79b7bf Thanks @segunadebayo! - - Fix issue where npmDependencies for snippets were not auto-installed
    • Support React Router 7 framework detection

3.2.0

Minor Changes

  • 069e39d Thanks @segunadebayo! - Add support for --all flag to add all snippets. By default, we only install a minimal/recommended set of snippets.

    Recommended snippets: provider, avatar, button, checkbox, radio, input-group, slider, popover, dialog, drawer, tooltip, field

    If you want to add all snippets, you can use the --all flag.

Patch Changes

  • a3ba8e6 Thanks @segunadebayo! - Fix issue where typegen doesn't work when CLI installed globally or run using npx

3.1.2

3.1.1

3.1.0

Patch Changes

  • baa3cb1 Thanks @segunadebayo! - Fix issue where adding a snippet with --outdir still creates snippets a src/components/ui directory.

3.0.2

Patch Changes

  • bfd9cac Thanks @segunadebayo! - Fix issue with vite setup where .mjs and mts files were not considered.

  • #9022 b40eb6b Thanks @Newbie012! - Fix issue where style props types show as any when using strictTokens

3.0.1

3.0.0

Minor Changes

  • 758f226 Thanks @segunadebayo! - Add support for composition command in CLI to import ready-made compositions for faster development experience.

    Usage: chakra-ui composition [options] [command]
    
    Add compositions to your project for better DX
    
    Options:
      -h, --help                     display help for command
    
    Commands:
      add [options] [components...]  Add a new composition for better DX
      list                           List all compositions
      help [command]                 display help for command
    
  • bfb68dc Thanks @segunadebayo! - Add eject command to import default theme into project

  • 085cacd Thanks @segunadebayo! - Add support for installing required NPM dependencies for compositions

  • 77fe01d Thanks @segunadebayo! - Change CLI name and command structure.

    • Change the CLI name from chakra-cli to chakra.
    • Change tokens command to typegen to better reflect its purpose since its generates types for more than just the tokens.
    • Scaffold new composition command to help users scaffold new compositions easily. Compositions are snippets of Chakra UI component composition them easier to reuse across projects.
  • 8fc7b49 Thanks @segunadebayo! - - Add support for conditional value in variant props.

    • Add @default JSDoc comment for defaultVariants in generated types.
  • 4ff153f Thanks @segunadebayo! - Speed up intellisence for style props, and add support for strictTokens in the CLI.

  • d50d72c Thanks @segunadebayo! - Rename compositions command to snippet for better intuitiveness

  • #8569 eb26857 Thanks @isBatak! - Fix the boxSize type to allow number values.

  • 14b6a45 Thanks @segunadebayo! - Show the number of skipped snippets that already exists in outdir

Patch Changes

3.0.0-next.32

3.0.0-next.31

3.0.0-next.30

3.0.0-next.29

Patch Changes

3.0.0-next.28

3.0.0-next.27

3.0.0-next.26

3.0.0-next.25

3.0.0-next.24

3.0.0-next.23

3.0.0-next.22

3.0.0-next.21

Minor Changes

3.0.0-next.20

Patch Changes

3.0.0-next.19

3.0.0-next.18

Minor Changes

  • bfb68dc Thanks @segunadebayo! - Add eject command to import default theme into project

  • 8fc7b49 Thanks @segunadebayo! - - Add support for conditional value in variant props.

    • Add @default JSDoc comment for defaultVariants in generated types.

3.0.0-next.17

3.0.0-next.16

Patch Changes

3.0.0-next.15

3.0.0-next.14

Minor Changes

3.0.0-next.13

3.0.0-next.12

Patch Changes

3.0.0-next.11

Minor Changes

  • 085cacd Thanks @segunadebayo! - Add support for installing required NPM dependencies for compositions

3.0.0-next.10

Minor Changes

  • 758f226 Thanks @segunadebayo! - Add support for composition command in CLI to import ready-made compositions for faster development experience.

    Usage: chakra-ui composition [options] [command]
    
    Add compositions to your project for better DX
    
    Options:
      -h, --help                     display help for command
    
    Commands:
      add [options] [components...]  Add a new composition for better DX
      list                           List all compositions
      help [command]                 display help for command
    

3.0.0-next.9

Minor Changes

  • 77fe01d Thanks @segunadebayo! - Change CLI name and command structure.
    • Change the CLI name from chakra-cli to chakra.
    • Change tokens command to typegen to better reflect its purpose since its generates types for more than just the tokens.
    • Scaffold new composition command to help users scaffold new compositions easily. Compositions are snippets of Chakra UI component composition them easier to reuse across projects.

3.0.0-next.8

3.0.0-next.7

Minor Changes

  • 4ff153f Thanks @segunadebayo! - Speed up intellisence for style props, and add support for strictTokens in the CLI.

3.0.0-next.6

3.0.0-next.5

Minor Changes

3.0.0-next.4

3.0.0-next.3

3.0.0-next.2

3.0.0-next.1

3.0.0-next.0

Patch Changes

2.4.1

Patch Changes

2.4.0

Minor Changes

  • #7494 27dcf2f56 Thanks @kuroppe1819! - Add support for nested semantic tokens in theme. It is now possible to declare semantic tokens by nesting objects.

    BEFORE:

    const theme = {
      semanticTokens: {
        colors: {
          "background.pressed.base": { default: "blue.800", _dark: "blue.300" },
          "background.pressed.subtle": { default: "blue.300", _dark: "blue.700" },
        },
      },
    }
    

    AFTER:

    const theme = {
      semanticTokens: {
        colors: {
          background: {
            pressed: {
              base: { default: "blue.800", _dark: "blue.300" },
              subtle: { default: "blue.300", _dark: "blue.700" },
            },
          },
        },
      },
    }
    

    This allows for cleaner grouping and organization of tokens.

2.3.1

Patch Changes

2.3.0

Minor Changes

  • #7127 ffc73f393 Thanks @lexanth! - - Added support for generating theme typings to use via module augmentation of the @chakra-ui/styled-system package.

    To use this feature, run the following command:

    chakra-cli tokens --template augmentation --out ./types/chakra-ui__styled-system.d.ts
    

2.2.1

Patch Changes

2.2.0

Minor Changes

  • #5701 eb3bfe66d Thanks @lexanth! - Add the flag --strict-token-types for @chakra-ui/cli tokens to generate strict types for theme tokens (e.g. color, spacing)

    chakra-cli tokens --strict-token-types
    
    // before
    <Box padding="abc" />
    // valid type, but "abc" is not available in the theme
    
    // after
    <Box padding="abc" /> // invalid
    // Type '"abc"' is not assignable to type '"1" | "2" | ... | undefined'.
    

2.1.8

Patch Changes

2.1.7

Patch Changes

2.1.6

Patch Changes

  • Force release

  • Updated dependencies []:

2.1.5

Patch Changes

2.1.4

Patch Changes

  • Force new release

  • Updated dependencies []:

2.1.3

Patch Changes

2.1.2

Patch Changes

2.1.1

Patch Changes

2.1.0

Minor Changes

  • #6117 154fee7f1 Thanks @TimKolberger! - New watch flag for the tokens command. You can specify a directory path to watch for changes. It defaults to the parent dir of <source>, e.g. src/theme/theme.ts => src/theme.

    > chakra-cli tokens src/theme/theme.ts --watch
    
    > chakra-cli tokens --help
    Usage: chakra-cli tokens [options] <source>
    
    Options:
      --out <path>              output file e.g. node_modules/@chakra-ui/styled-system/dist/declarations/src/theming.types.d.ts
      --strict-component-types  Generate strict types for props variant and size
      --watch [path]            Watch directory for changes and rebuild
      -h, --help                display help for command
    

Patch Changes

2.0.0

Major Changes

Patch Changes

2.0.0-next.2

Major Changes

Patch Changes

2.0.0-next.1

Major Changes

Patch Changes

1.9.1-next.0

Patch Changes

1.9.0

Minor Changes

1.8.2

Patch Changes

1.8.1

Patch Changes

1.8.0

Minor Changes

Patch Changes

1.7.1

Patch Changes

  • #5372 472612e7a Thanks @selbekk! - Update README to reflect the change of the default --out path to node_modules/@chakra-ui/styled-system/dist/declarations/src/theming.types.d.ts

  • Updated dependencies [1537a725f]:

1.7.0

Minor Changes

  • #5243 ae6fd7a25 Thanks @TimKolberger! - Use the feature flag --strict-component-types for @chakra-ui/cli tokens to generate strict component type for the theming props variant and size.

    chakra-cli tokens --strict-component-types
    
    // before
    <Button variant="abc" />
    // valid type but variant is not available in the theme
    
    // after
    <Button variant="abc" /> // invalid
    // Type '"abc"' is not assignable to type '"link" | "outline" | "ghost" | "solid" | "unstyled" | undefined'.
    

Patch Changes

1.6.0

Minor Changes

  • #4991 6095eaf9a Thanks @segunadebayo! - Update build system we use from a custom babel cli setup to preconstruct.

    The previous build system transpiles the code in src directory to dist/esm and dist/cjs keeping the same file structure. The new build system merges all files in src and transpiles to a single esm and cjs file.

    Potential Breaking Change: The side effect of this is that, if you imported any function, component or hook using the undocumented approach like import { useOutsideClick } from "@chakra-ui/hooks/dist/use-outside-click", you'll notice that the this doesn't work anymore.

    Here's how to resolve it:

    // Won't work 🎇
    import { useOutsideClick } from "@chakra-ui/hooks/dist/use-outside-click"
    
    // Works ✅
    import { useOutsideClick } from "@chakra-ui/hooks"
    

    If this affected your project, we recommend that you import hooks, functions or components the way it's shown in the documentation. This will help keep your project future-proof.

Patch Changes

1.5.3

Patch Changes

1.5.2

Patch Changes

1.5.1

Patch Changes

  • c96f44e16 #4725 Thanks @TimKolberger! - Fixed an issue where the CLI did not resolve custom tsconfig paths.

    🚨 Please note that only the first alias target from the string array will be resolved.

    // tsconfig.json
    {
      //...
      compilerOptions: {
        baseUrl: "src",
        paths: {
          "@alias/*": ["target/*"],
          //           ^-- only the first target will be resolved
        },
      },
    }
    

1.5.0

Minor Changes

Patch Changes

1.4.0

Minor Changes

  • fe2557584 #4067 Thanks @jrolfs! - The tokens command now supports generating theme token type definitions from a Chakra UI theme published as a package:

    npx @chakra-ui/cli tokens <@your-org/chakra-theme-package>
    

    A published theme package should export a theme object as either the default export or an export named theme.

    // chakra-theme-package/src/index.js
    import { extendTheme } from "@chakra-ui/react"
    
    const theme = extendTheme({})
    
    // as default export
    export default theme
    // as named export
    export { theme }
    

1.3.1

Patch Changes

  • e8f64a4a6 #3941 Thanks @jbarzegar! - Fixes issues with tokens command hanging forever if theme workers run into errors during runtime. Now when an error is discovered within a worker an { err: string } object is passed to the parent which will cause the promise to reject. This will in turn, pass the same err upwards to allow the command to exit gracefully, printing the err in question to stdout
  • Updated dependencies [d0f50a46e, b479ff22e, 07d15eab4]:

1.3.0

Minor Changes

Patch Changes

1.2.1

Patch Changes

1.2.0

Minor Changes

Patch Changes

1.1.0

Minor Changes