Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update multiple dependencies #114

Merged
merged 1 commit into from
Apr 27, 2023
Merged

Update multiple dependencies #114

merged 1 commit into from
Apr 27, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 27, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@babel/core (source) 7.21.0 -> 7.21.4 age adoption passing confidence
eslint (source) 8.35.0 -> 8.39.0 age adoption passing confidence
react-router-dom 6.8.2 -> 6.10.0 age adoption passing confidence
styled-components (source) 5.3.8 -> 5.3.10 age adoption passing confidence
webpack 5.75.0 -> 5.81.0 age adoption passing confidence
webpack-cli (source) 5.0.1 -> 5.0.2 age adoption passing confidence
webpack-dev-server 4.11.1 -> 4.13.3 age adoption passing confidence

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.


Release Notes

babel/babel

v7.21.4

Compare Source

🐛 Bug Fix
  • babel-core, babel-helper-module-imports, babel-preset-typescript
  • babel-generator
💅 Polish
  • babel-helper-create-class-features-plugin, babel-plugin-proposal-class-properties, babel-plugin-transform-typescript, babel-traverse
🏠 Internal

v7.21.3

Compare Source

👓 Spec Compliance
🐛 Bug Fix
💅 Polish
🏠 Internal
🔬 Output optimization
eslint/eslint

v8.39.0

Compare Source

Features

  • 3f7af9f feat: Implement SourceCode#markVariableAsUsed() (#​17086) (Nicholas C. Zakas)

Documentation

  • 6987dc5 docs: Fix formatting in Custom Rules docs (#​17097) (Milos Djermanovic)
  • 4ee92e5 docs: Update README (GitHub Actions Bot)
  • d8e9887 docs: Custom Rules cleanup/expansion (#​16906) (Ben Perlmutter)
  • 1fea279 docs: Clarify how to add to tsc agenda (#​17084) (Nicholas C. Zakas)
  • 970ef1c docs: Update triage board location (Nicholas C. Zakas)
  • 6d8bffd docs: Update README (GitHub Actions Bot)

Chores

v8.38.0

Compare Source

Features

  • a1d561d feat: Move getDeclaredVariables and getAncestors to SourceCode (#​17059) (Nicholas C. Zakas)

Bug Fixes

  • 1c1ece2 fix: do not report on RegExp(...args) in require-unicode-regexp (#​17037) (Francesco Trotta)

Documentation

  • 7162d34 docs: Mention new config system is complete (#​17068) (Nicholas C. Zakas)
  • 0fd6bb2 docs: Update README (GitHub Actions Bot)
  • c83531c docs: Update/remove external links, eg. point to eslint-community (#​17061) (Pelle Wessman)
  • a3aa6f5 docs: Clarify no-div-regex rule docs (#​17051) (Francesco Trotta)
  • b0f11cf docs: Update README (GitHub Actions Bot)
  • da8d52a docs: Update the second object instance for the "no-new" rule (#​17020) (Ahmadou Waly NDIAYE)
  • 518130a docs: switch language based on current path (#​16687) (Percy Ma)
  • 24206c4 docs: Update README (GitHub Actions Bot)

Chores

v8.37.0

Compare Source

Features

Bug Fixes

  • 619f3fd fix: correctly handle null default config in RuleTester (#​17023) (Brad Zacher)
  • 1fbf118 fix: getFirstToken/getLastToken on comment-only node (#​16889) (Francesco Trotta)
  • 129e252 fix: Fix typo in logical-assignment-operators rule description (#​17000) (Francesco Trotta)

Documentation

Chores

v8.36.0

Compare Source

Features

Bug Fixes

  • 92c1943 fix: correctly iterate files matched by glob patterns (#​16831) (Nitin Kumar)

Documentation

  • b98fdd4 docs: Update README (GitHub Actions Bot)
  • caf08ce docs: fix estree link in custom formatters docs (#​16967) (Milos Djermanovic)
  • 3398431 docs: Custom Parsers cleanup/expansion (#​16887) (Ben Perlmutter)
  • 19d3531 docs: Update README (GitHub Actions Bot)
  • b09a512 docs: detect and fix broken links (#​16837) (Nitin Kumar)

Chores

remix-run/react-router

v6.10.0

Compare Source

Minor Changes
  • Added support for Future Flags in React Router. The first flag being introduced is future.v7_normalizeFormMethod which will normalize the exposed useNavigation()/useFetcher() formMethod fields as uppercase HTTP methods to align with the fetch() behavior. (#​10207)

    • When future.v7_normalizeFormMethod === false (default v6 behavior),
      • useNavigation().formMethod is lowercase
      • useFetcher().formMethod is lowercase
    • When future.v7_normalizeFormMethod === true:
      • useNavigation().formMethod is uppercase
      • useFetcher().formMethod is uppercase
Patch Changes
  • Fix createStaticHandler to also check for ErrorBoundary on routes in addition to errorElement (#​10190)
  • Updated dependencies:
    • @remix-run/router@1.5.0
    • react-router@6.10.0

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
styled-components/styled-components

v5.3.10

Compare Source

What's Changed

Full Changelog: styled-components/styled-components@v5.3.9...v5.3.10

v5.3.9

Compare Source

What's Changed

Full Changelog: styled-components/styled-components@v5.3.8...v5.3.9

webpack/webpack

v5.81.0

Compare Source

New Features
Bug Fixes
Tests & Contributor Experience
Developer Experience
Dependencies & Maintenance
New Contributors

Full Changelog: webpack/webpack@v5.80.0...v5.81.0

v5.80.0

Compare Source

New Features

Bug Fixes

Tests & Contributor Experience

Developer Experience

Dependencies & Maintenance

New Contributors

Full Changelog: webpack/webpack@v5.79.0...v5.80.0

v5.79.0

Compare Source

New Features

Bugfixes

Developer Experience

Contributor Experience

New Contributors

Full Changelog: webpack/webpack@v5.78.0...v5.79.0

v5.78.0

Compare Source

Features

Bugfixes

Performance

Contributor Experience

Open in GitHub Codespaces

New Contributors

Full Changelog: webpack/webpack@v5.77.0...v5.78.0

v5.77.0

Compare Source

New Features

Developer Experience

Contributor Experience

New Contributors

Full Changelog: webpack/webpack@v5.76.3...v5.77.0

v5.76.3

Compare Source

Bugfixes

New Contributors

Full Changelog: webpack/webpack@v5.76.2...v5.76.3

v5.76.2

Compare Source

Bugfixes

Performance

Developer Experience


Configuration

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

🚦 Automerge: Enabled.

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.

@renovate renovate bot requested a review from Harmelodic as a code owner April 27, 2023 13:20
@renovate renovate bot merged commit fe78409 into main Apr 27, 2023
1 check passed
@renovate renovate bot deleted the renovate/multiple branch April 27, 2023 20:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants