chore(deps): bump the dependencies group across 1 directory with 8 updates

[dependabot]

Bumps the dependencies group with 8 updates in the / directory:

Package	From	To
@chakra-ui/react	2.8.2	3.0.2
date-fns	3.6.0	4.1.0
framer-motion	11.5.4	11.11.11
@types/react	18.3.5	18.3.12
@types/react-dom	18.3.0	18.3.1
@vitejs/plugin-react	4.3.1	4.3.3
typescript	5.6.2	5.6.3
wxt	0.19.9	0.19.13

Updates @chakra-ui/react from 2.8.2 to 3.0.2

Release notes

Sourced from @​chakra-ui/react's releases.

@​chakra-ui/react@​3.0.2

Patch Changes

• 20b91bd Thanks @​segunadebayo! - - InputAddon: Fix issue with input addon not stretched correctly.
  • Snippets / Toaster: Improve toaster styling by adding width={{ md: "sm" }} to the toast root.

@​chakra-ui/react@​3.0.1

Patch Changes

• c0020c9 Thanks @​segunadebayo! - Fix issue where using keyframe interpolation in animation prop doesn't work

• 7d4f898 Thanks @​segunadebayo! - Fix issue where scrollBehavior=outside doesn't allow scrolling outside the dialog content

@​chakra-ui/react@​3.0.0

Major Changes

• #8153 7b6e66a Thanks @​segunadebayo! - Prepares the ground for the next version Chakra that leverages Ark UI.

  User Facing

  • Consolidate all component packages into a single package
  • Remove all deprecated components and APIs
  • Simplify the Changelogs for all v2 releases

  Infrastructure

  • Simplify the repo infrastructure and release process
  • Migrate from jest to vitest
  • Migrate from tsup to custom rollup setup for better bundling strategy

• #8815 806be96 Thanks @​isBatak! - Remove the @chakra-ui/hooks package in favour of using dedicated, robust libraries like react-use and usehooks-ts

Minor Changes

• #8121 170198f

... (truncated)

Changelog

Sourced from @​chakra-ui/react's changelog.

3.0.2

Patch Changes

• 20b91bd Thanks @​segunadebayo! - - InputAddon: Fix issue with input addon not stretched correctly.
  • Snippets / Toaster: Improve toaster styling by adding width={{ md: "sm" }} to the toast root.

3.0.1

Patch Changes

• c0020c9 Thanks @​segunadebayo! - Fix issue where using keyframe interpolation in animation prop doesn't work

• 7d4f898 Thanks @​segunadebayo! - Fix issue where scrollBehavior=outside doesn't allow scrolling outside the dialog content

3.0.0

Major Changes

• #8153 7b6e66a Thanks @​segunadebayo! - Prepares the ground for the next version Chakra that leverages Ark UI.

  User Facing

  • Consolidate all component packages into a single package
  • Remove all deprecated components and APIs
  • Simplify the Changelogs for all v2 releases

  Infrastructure

  • Simplify the repo infrastructure and release process
  • Migrate from jest to vitest
  • Migrate from tsup to custom rollup setup for better bundling strategy

• #8815 806be96 Thanks @​isBatak! - Remove the @chakra-ui/hooks package in favour of using dedicated, robust libraries like react-use and usehooks-ts

Minor Changes

... (truncated)

Commits

• 4f34540 Version Packages (#9019)
• 20b91bd chore: update toaster and input addon
• f40e7bb Version Packages (#8996)
• 876b213 docs: add next changelog
• c0020c9 fix(system): emotion keyframe interpolation
• 7d4f898 fix(dialog): scroll behavior outside
• cb31f74 docs: add random color example
• d0f502f Version Packages (#8962)
• 738cdd2 chore(select): update item group styling
• a29d422 Version Packages (next) (#8956)
• Additional commits viewable in compare view

Updates date-fns from 3.6.0 to 4.1.0

Release notes

Sourced from date-fns's releases.

v4.1.0

This release adds time zone support to format functions (that I somehow missed when working on the feature) and fixes a few bugs.

Make sure also upgrade TZDate to v1.0.2 as it includes a bunch of critical bug fixes.

Fixed

• Fixed internal constructFrom throwing an exception on null arguments. While null isn't allowed, the functions should rather return Invalid Date or NaN in such cases. See #3885.

Added

• Added missing time zone support to format, formatISO, formatISO9075, formatRelative and formatRFC3339. See #3886.

v4.0.0

I have great news! First, ten years after its release, date-fns finally gets first-class time zone support.

Another great news is that there aren't many breaking changes in this release. All of them are type-related and will affect only those explicitly using internal date-fns types. Finally, it has been less than a year since the last major release, which is an improvement over the previous four years between v2 and v3. I plan on keeping the pace and minimizing breaking changes moving forward.

Read more about the release in the announcement blog post.

- Sasha @​kossnocorp

Added

• Added time zones support via @date-fns/tz's TZDate class and tz helper function. See its README for the details about the API.

• All relevant functions now accept the context in option, which allows to specify the time zone to make the calculations in. If the function also returns a date, it will be in the specified time zone:

  import { addDays, startOfDay } from "date-fns";
  import { tz } from "@date-fns/tz";
  startOfDay(addDays(Date.now(), 5, { in: tz("Asia/Singapore") }));
  //=> "2024-09-16T00:00:00.000+08:00"

  In the example, addDays will get the current date and time in Singapore and add 5 days to it. startOfDay will inherit the date type and return the start of the day in Singapore.

Changed

• The function arguments, as well as Interval's start and end, now can be of different types, allowing you to mix UTCDate, TZDate, Date, and other extensions, as well as primitives (strings and numbers).

  The functions will normalize these values, make calculations, and return the result in the same type, preventing any bugs caused by the discrepancy. If passed, the type will be inferred from the context in option or the first encountered argument object type. The Interval's start and end will be considered separately, starting from start.

  In the given example, the result will be in the TZDate as the first argument is a number, and the start takes precedence over the end.

  clamp(Date.now(), {
    start: new TZDate(start, "Asia/Singapore"),
    end: new UTCDate(),

... (truncated)

Changelog

Sourced from date-fns's changelog.

v4.1.0 - 2024-09-17

This release adds time zone support to format functions (that I somehow missed when working on the feature) and fixes a few bugs.

Make sure also upgrade TZDate to v1.0.2 as it includes a bunch of critical bug fixes.

Fixed

• Fixed internal constructFrom throwing an exception on null arguments. While null isn't allowed, the functions should rather return Invalid Date or NaN in such cases. See #3885.

Added

• Added missing time zone support to format, formatISO, formatISO9075, formatRelative and formatRFC3339. See #3886.

v4.0.0 - 2024-09-16

I have great news! First, ten years after its release, date-fns finally gets first-class time zone support.

Another great news is that there aren't many breaking changes in this release. All of them are type-related and will affect only those explicitly using internal date-fns types. Finally, it has been less than a year since the last major release, which is an improvement over the previous four years between v2 and v3. I plan on keeping the pace and minimizing breaking changes moving forward.

Read more about the release in the announcement blog post.

- Sasha @​kossnocorp

Added

• Added time zones support via @date-fns/tz's TZDate class and tz helper function. See its README for the details about the API.

• All relevant functions now accept the context in option, which allows to specify the time zone to make the calculations in. If the function also returns a date, it will be in the specified time zone:

  import { addDays, startOfDay } from "date-fns";
  import { tz } from "@date-fns/tz";
  startOfDay(addDays(Date.now(), 5, { in: tz("Asia/Singapore") }));
  //=> "2024-09-16T00:00:00.000+08:00"

  In the example, addDays will get the current date and time in Singapore and add 5 days to it. startOfDay will inherit the date type and return the start of the day in Singapore.

Changed

• The function arguments, as well as Interval's start and end, now can be of different types, allowing you to mix UTCDate, TZDate, Date, and other extensions, as well as primitives (strings and numbers).

  The functions will normalize these values, make calculations, and return the result in the same type, preventing any bugs caused by the discrepancy. If passed, the type will be inferred from the context in option or the first encountered argument object type. The Interval's start and end will be considered separately, starting from start.

  In the given example, the result will be in the TZDate as the first argument is a number, and the start takes precedence over the end.

  clamp(Date.now(), {

... (truncated)

Commits

• 313b902 Fix v4.1.0 change log entry
• 26cd336 Promote to v4.1.0
• 97b53b9 Cover time zone edge cases
• 59b7563 Add missing time zone support to format, formatISO, formatISO9075, formatRela...
• 0121164 Prevent constructFrom from throwing an error on null
• bd87ef5 Update @​date-fns/docs
• 99b4e67 Prepare v4.0
• 8df1706 Rewrite the time zones doc
• e351977 Promote to v4.0.0-beta.1
• 8523656 Fix scripts/test/types.sh
• Additional commits viewable in compare view

Updates framer-motion from 11.5.4 to 11.11.11

Changelog

Sourced from framer-motion's changelog.

[11.11.11] 2024-10-31

Fixed

• Fixing double update() call on mount.

[11.11.10] 2024-10-25

Fixed

• Removing will-change from SSR.

[11.11.9] 2024-10-15

Changed

• will-change is now no longer automatically managed without useWillChange.

[11.11.8] 2024-10-11

Fixed

• Fixing fallback package.json for entrypoints in older versions of Node.

[11.11.7] 2024-10-09

Fixed

• Improving generic value signature for animate.

[11.11.6] 2024-10-09

Fixed

• Allowing generic motion value types in animate.

[11.11.5] 2024-10-09

Fixed

• Removed ability to define CSS variables on style without casting, as this was conflicting with React CSSProperties.

[11.11.4] 2024-10-08

Fixed

• Memoize AnimatePresence safeToRemove.
• Remove duplicate layout="size" annotation.

[11.11.3] 2024-10-08

... (truncated)

Commits

• 1ed8397 v11.11.11
• 4cd1527 Updating changelog
• f3468b3 Merge pull request #2852 from framer/fix/double-mount-update
• c3593da Fixing
• 1e7f9df Fix double .update() call on mount
• c02ec5a v11.11.10
• 1232e7c Updating changelog
• 1cf39c7 Merge pull request #2845 from framer/fix/ssr-will-change
• 0325534 Updating test
• 5507ae3 Refactor
• Additional commits viewable in compare view

Updates @types/react from 18.3.5 to 18.3.12

Commits

• See full diff in compare view

Updates @types/react-dom from 18.3.0 to 18.3.1

Commits

• See full diff in compare view

Updates @vitejs/plugin-react from 4.3.1 to 4.3.3

Release notes

Sourced from @​vitejs/plugin-react's releases.

v4.3.3

React Compiler runtimeModule option removed

React Compiler was updated to accept a target option and runtimeModule was removed. vite-plugin-react will still detect runtimeModule for backwards compatibility.

When using a custom runtimeModule or target !== '19', the plugin will not try to pre-optimize react/compiler-runtime dependency.

The react-compiler-runtime is now available on npm can be used instead of the local shim for people using the compiler with React < 19.

Here is the configuration to use the compiler with React 18 and correct source maps in development:

npm install babel-plugin-react-compiler react-compiler-runtime @babel/plugin-transform-react-jsx-development

export default defineConfig(({ command }) => {
  const babelPlugins = [['babel-plugin-react-compiler', { target: '18' }]]
  if (command === 'serve') {
    babelPlugins.push(['@babel/plugin-transform-react-jsx-development', {}])
  }
return {
plugins: [react({ babel: { plugins: babelPlugins } })],
}
})

v4.3.2

Ignore directive sourcemap error #369

Changelog

Sourced from @​vitejs/plugin-react's changelog.

4.3.3 (2024-10-19)

React Compiler runtimeModule option removed

React Compiler was updated to accept a target option and runtimeModule was removed. vite-plugin-react will still detect runtimeModule for backwards compatibility.

When using a custom runtimeModule or target !== '19', the plugin will not try to pre-optimize react/compiler-runtime dependency.

The react-compiler-runtime is now available on npm can be used instead of the local shim for people using the compiler with React < 19.

Here is the configuration to use the compiler with React 18 and correct source maps in development:

npm install babel-plugin-react-compiler react-compiler-runtime @babel/plugin-transform-react-jsx-development

export default defineConfig(({ command }) => {
  const babelPlugins = [['babel-plugin-react-compiler', { target: '18' }]]
  if (command === 'serve') {
    babelPlugins.push(['@babel/plugin-transform-react-jsx-development', {}])
  }
return {
plugins: [react({ babel: { plugins: babelPlugins } })],
}
})

4.3.2 (2024-09-29)

Ignore directive sourcemap error #369

Commits

• b61592a release: [email protected]
• e8a923f fix: add react-dom in optimizeOps to handle CJS script. (#375)
• 7a7e339 feat: support new React Compiler target option (#374)
• 63b2e38 release: [email protected]
• fdf6ce4 fix(deps): update all non-major dependencies (#273)
• 4544e97 feat: update refresh utils for React Router 7 support (#363)
• d88c581 fix: ignore directive sourcemap error (#369)
• See full diff in compare view

Updates typescript from 5.6.2 to 5.6.3

Release notes

Sourced from typescript's releases.

TypeScript 5.6.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.6.0 (Beta).
• fixed issues query for Typescript 5.6.1 (RC).
• fixed issues query for Typescript 5.6.2 (Stable).
• fixed issues query for Typescript 5.6.3 (Stable).

Downloads are available on:

• npm
• NuGet package

Commits

• d48a5cf Bump version to 5.6.3 and LKG
• fefa70a 🤖 Pick PR #60083 (Don't issue implicit any when obtai...) into release-5.6 (#...
• ff71692 [release-5.6] Remove tsbuildInfo specification error now that we need it for ...
• 1f44dcf 🤖 Pick PR #60157 (fix automatic type acquisition) into release-5.6 (#60169)
• See full diff in compare view

Updates wxt from 0.19.9 to 0.19.13

Release notes

Sourced from wxt's releases.

wxt v0.19.13

compare changes

🚀 Enhancements

• env: Load env from .env.[browser] variants (#1078)

🩹 Fixes

• Don't use #private member variables in ContentScriptContext (#1103)

❤️ Contributors

• Aaron (@​aklinker1)
• Craig Slusher (@​sleekslush)

wxt v0.19.12

compare changes

🚀 Enhancements

• Add support for WXT_ environment variable prefix (#1076)
• config: Add outDirTemplate for customizing output directory structure (#1074)

🔥 Performance

• Replace execa with nano-spawn for smaller package size (#1042)
• Downgrade esbuild so a single version is shared between sub-dependencies (#1045)

🩹 Fixes

• Use directory name when zip.name and package.json#name are not provided (#1028)
• Ensure consistent hook execution order and add docs (#1081)

📖 Documentation

• Rewrite and restructure the documentation website (#933)

🏡 Chore

• Remove email from changelog (#1027)
• deps: Bump magicast from 0.3.4 to 0.3.5 (#1017)
• deps: Bump esbuild from 0.23.0 to 0.24.0 (#1018)
• deps: Bump linkedom from 0.18.4 to 0.18.5 (#1034)
• deps: Bump execa from 9.3.1 to 9.4.0 (#1031)
• Upgrade all non-major dependencies (#1040)
• Shrink down on dependencies (#1050)
• Enable extensionApi: chrome in template projects (#1083)

❤️ Contributors

... (truncated)

Commits

• ae1e276 chore(release): wxt v0.19.13
• c031c6e feat(env): Load env from .env.[browser] variants (#1078)
• d06f812 enhance(docs): comparison to real footnotes (#1096)
• 6ba12e9 feat: unocss module (#1043)
• 0092556 fix: Don't use #private member variables in ContentScriptContext (#1103)
• 9721bca docs: Add "Sync Watch" extension to homepage (#1098)
• 1b138f8 docs: Remove duplicate env data
• e839671 chore(release): wxt v0.19.12
• 842c158 chore: Enable extensionApi: chrome in template projects (#1083)
• b14c910 chore(release): @​wxt-dev/i18n v0.2.1
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions