Skip to content
This repository has been archived by the owner on Nov 30, 2023. It is now read-only.

chore(deps): update chakra-ui monorepo to v2 (major) #539

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 17, 2022

Mend Renovate logo banner

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@chakra-ui/icons ^1.0.13 -> ^2.0.0 age adoption passing confidence
@chakra-ui/react (source) ^1.6.3 -> ^2.0.0 age adoption passing confidence

Release Notes

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

v2.1.1

Compare Source

Patch Changes

v2.1.0

Compare Source

Minor Changes
  • 754d9d4f4
    Thanks @​segunadebayo! - To improve support
    for the App Router, all components and hooks are exported with the
    "use client" directive.
Patch Changes

v2.0.19

Compare Source

Patch Changes

v2.0.18

Patch Changes

v2.0.17

Patch Changes

v2.0.16

Compare Source

Patch Changes

v2.0.15

Compare Source

Patch Changes
  • #​7154
    2d7398a01
    Thanks @​segunadebayo! - ## All components

    Improved the bundling setup for all components.

    • Switched to the .mjs file extension for correct ESM behavior
    • Switched to the latest tsup will uses automatic JSX runtime detection
      removing the need for manually inject classic React import
    • Moved tsup config to package.json since it's very minimal
    • Removed clean-package.config.json in favor of the package.json property
    • Fixed issue where Storybook addon (dark mode and RTL) was not working
  • Updated dependencies
    [2d7398a01]:

v2.0.14

Compare Source

Patch Changes

v2.0.13

Compare Source

Patch Changes

v2.0.12

Compare Source

Patch Changes

v2.0.11

Compare Source

Patch Changes

v2.0.10

Compare Source

Patch Changes

v2.0.9

Patch Changes

v2.0.8

Patch Changes

v2.0.7

Patch Changes

v2.0.6

Patch Changes

v2.0.5

Patch Changes

v2.0.4

Compare Source

Patch Changes

v2.0.3

Compare Source

Patch Changes

v2.0.2

Compare Source

Patch Changes

v2.0.1

Compare Source

Patch Changes

v2.0.0

Compare Source

Major Changes
Patch Changes

v1.1.7

Compare Source

Patch Changes

v1.1.6

Compare Source

Patch Changes

v1.1.5

Compare Source

Patch Changes

v1.1.4

Compare Source

Patch Changes

v1.1.3

Compare Source

Patch Changes

v1.1.2

Compare Source

Patch Changes

v1.1.1

Compare Source

Patch Changes

v1.1.0

Compare Source

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

v1.0.17

Compare Source

Patch Changes

v1.0.16

Compare Source

Patch Changes

v1.0.15

Compare Source

Patch Changes

v1.0.14

Compare Source

Patch Changes
chakra-ui/chakra-ui (@​chakra-ui/react)

v2.8.2

Compare Source

Patch Changes

v2.8.1

Compare Source

Patch Changes

v2.8.0

Compare Source

Minor Changes
  • 754d9d4f4
    Thanks @​segunadebayo! - To improve support
    for the App Router, all components and hooks are exported with the
    "use client" directive.
Patch Changes

v2.7.1

Compare Source

Patch Changes
  • #​7730
    2456a7090
    Thanks @​TylerAPfledderer! - Expose the
    skip nav components and types to the main package

    import {
      SkipNavLink,
      type SkipNavLinkProps,
      SkipNavContent,
      type SkipNavContentProps,
    } from "@​chakra-ui/react"

v2.7.0

Compare Source

Minor Changes
  • c31df5a4b
    Thanks @​segunadebayo! - - Add new
    Indicator layout component. Useful for positioning an element in the corners
    of another element.

    For example, let's say you want to position a notification badge in the top
    end corner of a box. You can use the Indicator component to achieve this.

    <Box position="relative" width="80px" height="80px" bg="gray.50">
      <Indicator placement="top-end">
        <Circle size="5" bg="red.100">
          3
        </Circle>
      </Indicator>
    </Box>
    • Refactored the Stack and Wrap components to use the flex gap instead of
      the owl selector & > * ~ * for spacing.

      This fixes an issue where you can't use raw text nodes as a child of the
      Stack or Wrap component.

Patch Changes

v2.6.1

Compare Source

Patch Changes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

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


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

This PR has been generated by Mend Renovate. View repository job log here.

@cloudflare-workers-and-pages
Copy link

Deploying with  Cloudflare Pages  Cloudflare Pages

Latest commit: 2a2113a
Status:🚫  Build failed.

View logs

@renovate renovate bot changed the title Update chakra-ui monorepo to v2 (major) chore(deps): update chakra-ui monorepo to v2 (major) Dec 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants