Update dependency @chakra-ui/cli to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@chakra-ui/cli	^2.4.1 -> ^3.0.0

---

Release Notes

chakra-ui/chakra-ui (@​chakra-ui/cli)

v3.1.2

Compare Source

v3.1.1

Compare Source

v3.1.0

Compare Source

Minor Changes

• #​7096
  3547207e5
  Thanks @​TylerAPfledderer! - Add option
  to use ChakraBaseProvider instead of ChakraProvider. This will only apply
  theme tokens initially and not default theming for components.

v3.0.2

Compare Source

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

v3.0.1

Compare Source

v3.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

• 0eda15c
  Thanks @​segunadebayo! - Set process
  setMaxListeners to improve watch mode

• c074b58
  Thanks @​segunadebayo! - Fix issue where
  vite project throws due to config search

• 0f0ed76
  Thanks @​segunadebayo! - Fix regression
  where files were always converted to .jsx

• #​8740
  d5a225f
  Thanks @​Pagebakers! - Use correct extension
  for ESM exports

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - "at 10am on Monday except on 25th of December in 2023 and 1st of January 2024 and 1st of April 2024 and 20th of May 2024 and 19th of August 2024" (UTC).

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

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

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

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: @chakra-ui/[email protected]
npm error node_modules/@chakra-ui/react
npm error   @chakra-ui/react@"^2.8.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @chakra-ui/react@">=3.0.0-next.0" from @chakra-ui/[email protected]
npm error node_modules/@chakra-ui/cli
npm error   dev @chakra-ui/cli@"^3.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-11-18T03_42_14_989Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-11-18T03_42_14_989Z-debug-0.log