fix(deps): update dependencies (non-major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@capacitor/core (source)	4.7.0 -> 4.7.1
@capacitor/ios (source)	4.7.0 -> 4.7.1
@mui/lab (source)	5.0.0-alpha.121 -> 5.0.0-alpha.124
@mui/material (source)	5.11.11 -> 5.11.14
@mui/system (source)	5.11.11 -> 5.11.14
i18next (source)	22.4.10 -> 22.4.13
i18next-http-backend	2.1.1 -> 2.2.0
react-router-dom	6.8.2 -> 6.9.0
slate-react	0.91.8 -> 0.92.0
zustand	4.3.3 -> 4.3.6

---

Release Notes

ionic-team/capacitor

v4.7.1

Compare Source

Bug Fixes

• cli: point build to proper workspace name (#​6373) (81af12a)
• iOS: Separate cookies by ; rather than ; when accessing through document.cookie (Cap 4.x) (#​6380) (1902b77)

mui/material-ui

v5.0.0-alpha.124

Compare Source

• [Masonry] Include Masonry in theme augmentation interface (#​36533) @​hbjORbj

v5.0.0-alpha.123

Compare Source

v5.0.0-alpha.122

Compare Source

• ​[TreeView] Fix Tree View inside shadow root crashes (#​36225) @​NoFr1ends

i18next/i18next

v22.4.13

Compare Source

• fix: deepFind as fallback for interpolation 1930

v22.4.12

Compare Source

• fix: getBestMatchFromCodes when dev is a supported lng 1927

v22.4.11

Compare Source

• types: fix postProcessor key argument type, fixes 1919

i18next/i18next-http-backend

v2.2.0

Compare Source

• parseLoadPayload for POST request 110

remix-run/react-router

v6.9.0

Compare Source

Minor Changes

• React Router now supports an alternative way to define your route element and errorElement fields as React Components instead of React Elements. You can instead pass a React Component to the new Component and ErrorBoundary fields if you choose. There is no functional difference between the two, so use whichever approach you prefer 😀. You shouldn't be defining both, but if you do Component/ErrorBoundary will "win". (#​10045)

  Example JSON Syntax

  // Both of these work the same:
  const elementRoutes = [{
    path: '/',
    element: <Home />,
    errorElement: <HomeError />,
  }]
  
  const componentRoutes = [{
    path: '/',
    Component: Home,
    ErrorBoundary: HomeError,
  }]
  
  function Home() { ... }
  function HomeError() { ... }

  Example JSX Syntax

  // Both of these work the same:
  const elementRoutes = createRoutesFromElements(
    <Route path='/' element={<Home />} errorElement={<HomeError /> } />
  );
  
  const componentRoutes = createRoutesFromElements(
    <Route path='/' Component={Home} ErrorBoundary={HomeError} />
  );
  
  function Home() { ... }
  function HomeError() { ... }

• Introducing Lazy Route Modules! (#​10045)

  In order to keep your application bundles small and support code-splitting of your routes, we've introduced a new lazy() route property. This is an async function that resolves the non-route-matching portions of your route definition (loader, action, element/Component, errorElement/ErrorBoundary, shouldRevalidate, handle).

  Lazy routes are resolved on initial load and during the loading or submitting phase of a navigation or fetcher call. You cannot lazily define route-matching properties (path, index, children) since we only execute your lazy route functions after we've matched known routes.

  Your lazy functions will typically return the result of a dynamic import.

  // In this example, we assume most folks land on the homepage so we include that
  // in our critical-path bundle, but then we lazily load modules for /a and /b so
  // they don't load until the user navigates to those routes
  let routes = createRoutesFromElements(
    <Route path="/" element={<Layout />}>
      <Route index element={<Home />} />
      <Route path="a" lazy={() => import("./a")} />
      <Route path="b" lazy={() => import("./b")} />
    </Route>
  );

  Then in your lazy route modules, export the properties you want defined for the route:

  export async function loader({ request }) {
    let data = await fetchData(request);
    return json(data);
  }
  
  // Export a `Component` directly instead of needing to create a React Element from it
  export function Component() {
    let data = useLoaderData();
  
    return (
      <>
        <h1>You made it!</h1>
        <p>{data}</p>
      </>
    );
  }
  
  // Export an `ErrorBoundary` directly instead of needing to create a React Element from it
  export function ErrorBoundary() {
    let error = useRouteError();
    return isRouteErrorResponse(error) ? (
      <h1>
        {error.status} {error.statusText}
      </h1>
    ) : (
      <h1>{error.message || error}</h1>
    );
  }

  An example of this in action can be found in the examples/lazy-loading-router-provider directory of the repository.

  🙌 Huge thanks to @​rossipedia for the Initial Proposal and POC Implementation.

• Updated dependencies:

  • react-router@6.9.0
  • @remix-run/router@1.4.0

ianstormtaylor/slate

v0.92.0

Compare Source

Minor Changes

• #​5363 d42cd005 Thanks @​aciccarello! - update dependencies on react hooks to be more senstive to changes

  The code should now meet eslint react hook standards

  This could result in more renders

  closes #​3886

Patch Changes

• #​5369 556a4565 Thanks @​alex-vladut! - Allow copying from editable void input

v0.91.11

Compare Source

Patch Changes

• #​5362 43999356 Thanks @​jason0x43! - Fix an issue where pastes in Safari wouldn't include application/x-slate-fragment data

• #​5359 9825d29b Thanks @​jason0x43! - Fix an issue on Android where content containing a newline wouldn't be pasted properly

v0.91.10

Compare Source

Patch Changes

• #​5346 a5e833f6 Thanks @​edhager! - Fix a problem with Editable not calling the decorate function passed as a prop when it should.

• #​5343 f7f02a8b Thanks @​12joan! - Fix error when triple-clicking a word preceding a contenteditable="false" DOM node in Chrome

v0.91.9

Compare Source

Patch Changes

• #​5339 62f8ddd9 Thanks @​12joan! - Fixes #​5335. To prevent performance issues, make sure to wrap custom renderPlaceholder values in useCallback.

pmndrs/zustand

v4.3.6

Compare Source

This has a little improvement for library authors.

What's Changed

• fix(react, types): relax react types by @​lukesmurray in https://github.com/pmndrs/zustand/pull/1589
• fix: typo in shallow.ts by @​ysulyma in https://github.com/pmndrs/zustand/pull/1667

New Contributors

• @​ctolmsted made their first contribution in https://github.com/pmndrs/zustand/pull/1670
• @​kevin51jiang made their first contribution in https://github.com/pmndrs/zustand/pull/1674
• @​lukesmurray made their first contribution in https://github.com/pmndrs/zustand/pull/1589
• @​ysulyma made their first contribution in https://github.com/pmndrs/zustand/pull/1667

Full Changelog: pmndrs/zustand@v4.3.5...v4.3.6

v4.3.5

Compare Source

v4.3.4 has a regression in CJS build. Please use this version instead.

What's Changed

• fix(build): re-export createStore from index by @​hiendv in https://github.com/pmndrs/zustand/pull/1661

New Contributors

• @​jmantonellini made their first contribution in https://github.com/pmndrs/zustand/pull/1485
• @​hiendv made their first contribution in https://github.com/pmndrs/zustand/pull/1661

Full Changelog: pmndrs/zustand@v4.3.4...v4.3.5

v4.3.4

Compare Source

This version fixes some build configs for some edge cases.

⚠️ this version has an issue in CJS build. Please use v4.3.5.

What's Changed

• fix(build): UMD names by @​dai-shi in https://github.com/pmndrs/zustand/pull/1632
• fix(build): possibly improve ESM for production build by @​dai-shi in https://github.com/pmndrs/zustand/pull/1645
• fix(build): add explicit export paths for cjs by @​barelyhuman in https://github.com/pmndrs/zustand/pull/1659

New Contributors

• @​AwesomeDevin made their first contribution in https://github.com/pmndrs/zustand/pull/1633
• @​adimit made their first contribution in https://github.com/pmndrs/zustand/pull/1641

Full Changelog: pmndrs/zustand@v4.3.3...v4.3.4

---

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
2do-txt	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Mar 28, 2023 at 4:40PM (UTC)

[github-actions]

🎉 This PR is included in version 1.17.8 🎉

The release is available on:

• GitHub release
• v1.17.8

Your semantic-release bot 📦🚀