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.

Sign up for GitHub

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

Jump to bottom

fix(deps): update all non-major dependencies #126

Merged
merged 1 commit into from
Jul 3, 2023
Merged

fix(deps): update all non-major dependencies #126

merged 1 commit into from
Jul 3, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 3, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@generouted/react-router ^1.13.6 -> ^1.15.0 age adoption passing confidence
@swc/core (source) ^1.3.66 -> ^1.3.67 age adoption passing confidence
@types/node (source) ^18.16.18 -> ^18.16.19 age adoption passing confidence
esbuild ^0.18.9 -> ^0.18.11 age adoption passing confidence
pnpm (source) 8.6.4 -> 8.6.5 age adoption passing confidence
react-router-dom ^6.14.0 -> ^6.14.1 age adoption passing confidence
typescript (source) ^5.1.3 -> ^5.1.6 age adoption passing confidence

Release Notes

oedotme/generouted (@​generouted/react-router)

v1.15.0

Compare Source

Changes

Introduce route-based and app-level Pending component as a Suspense fallback for both @generouted/react-router and @generouted/solid-router

export const Pending = () => <div>Loading...</div>
Breaking change 🚨

For @generouted/solid-router, now the routes tree/object has the src/pages/_app.tsx as the root route and all the routes render as children like the current implement for @generouted/react-router.

You need to make two changes only at src/pages/_app.tsx for this new update:

  • Render an <Outlet /> component from @solidjs/router instead of {props.children}
  • Render the <Modals /> component explicitly, it was included previously at the exported <Routes /> component
// src/pages/_app.tsx

import { Outlet } from '@&#8203;solidjs/router'
import { Modals } from '@&#8203;generouted/solid-router'

import { useModals } from '../router'

export default function App() {
  const modals = useModals()

  return (
    <section>
      <header>
        <nav>...</nav>
        <button onClick={() => modals.open('/login')}>Open modal</button>
      </header>

      <main>
        <Outlet />
      </main>

      <Modals />
    </section>
  )
}

Commits

Changelog: oedotme/generouted@v1.14.0...v1.15.0

v1.14.0

Compare Source

Changes

You can now export an app level error boundary Catch component from src/pages/_app.tsx with the following integrations:

  • @generouted/react-router, @generouted/react-router/lazy
// src/pages/_app.tsx

export const Catch = () => <div>...</div>
  • @generouted/solid-router, @generouted/solid-router/lazy
// src/pages/_app.tsx

export const Catch = (props: { error: Error; reset: () => void }) => <div>...</div>
Breaking changes 🚨

If you're using the generatePreservedRoutes directly from the core functions or through a custom integration you should now access the default export explicitly:

const preservedRoutes = generatePreservedRoutes(PRESERVED)

-const App = preservedRoutes?.['_app'] || Outlet
-const NotFound = preservedRoutes?.['404'] || Fragment
+const App = preservedRoutes?.['_app']?.default || Outlet
+const NotFound = preservedRoutes?.['404']?.default || Fragment

Commits

Changelog: oedotme/generouted@v1.13.7...v1.14.0

v1.13.7

Compare Source

Changes

  • Setup issue template
  • Updated docs structure, content and conventions example
  • Add file-based Catch component with error boundary for Solid integrations
export const Catch = (props: { error: Error; reset: () => void }) => <div>...</div>

Commits

Changelog: oedotme/generouted@v1.13.6...v1.13.7

swc-project/swc (@​swc/core)

v1.3.67

Compare Source

Bug Fixes

  • (es/minifier) Don't drop assignments to unused top-level variables (#​7581) (a685c88)

  • (es/parser) Adjust context while parsing type arguments of TypeScript type queries (#​7582) (9d5dda1)

  • (estree/compat) Adjust loc.col (#​7565) (d86f8f6)

Features
Miscellaneous Tasks
Refactor
Build
evanw/esbuild (esbuild)

v0.18.11

Compare Source

  • Fix a TypeScript code generation edge case (#​3199)

    This release fixes a regression in version 0.18.4 where using a TypeScript namespace that exports a class declaration combined with --keep-names and a --target of es2021 or earlier could cause esbuild to export the class from the namespace using an incorrect name (notice the assignment to X2._Y vs. X2.Y):

    // Original code

// Old output (with --keep-names --target=es2021)
var X;
((X2) => {
  const _Y = class _Y {
  };
  __name(_Y, "Y");
  let Y = _Y;
  X2._Y = _Y;
})(X || (X = {}));

// New output (with --keep-names --target=es2021)
var X;
((X2) => {
  const _Y = class _Y {
  };
  __name(_Y, "Y");
  let Y = _Y;
  X2.Y = _Y;
})(X || (X = {}));

v0.18.10

Compare Source

  • Fix a tree-shaking bug that removed side effects (#​3195)

    This fixes a regression in version 0.18.4 where combining --minify-syntax with --keep-names could cause expressions with side effects after a function declaration to be considered side-effect free for tree shaking purposes. The reason was because --keep-names generates an expression statement containing a call to a helper function after the function declaration with a special flag that makes the function call able to be tree shaken, and then --minify-syntax could potentially merge that expression statement with following expressions without clearing the flag. This release fixes the bug by clearing the flag when merging expression statements together.

  • Fix an incorrect warning about CSS nesting (#​3197)

    A warning is currently generated when transforming nested CSS to a browser that doesn't support :is() because transformed nested CSS may need to use that feature to represent nesting. This was previously always triggered when an at-rule was encountered in a declaration context. Typically the only case you would encounter this is when using CSS nesting within a selector rule. However, there is a case where that's not true: when using a margin at-rule such as @top-left within @page. This release avoids incorrectly generating a warning in this case by checking that the at-rule is within a selector rule before generating a warning.

pnpm/pnpm (pnpm)

v8.6.5

Compare Source

Patch Changes

  • Improve the performance of searching for auth tokens #​6717.

Our Gold Sponsors

Our Silver Sponsors
remix-run/react-router (react-router-dom)

v6.14.1

Compare Source

Patch Changes
Microsoft/TypeScript (typescript)

v5.1.5: TypeScript 5.1.5

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Jul 3, 2023
@ArnaudBarre ArnaudBarre merged commit 8035a16 into main Jul 3, 2023
1 check passed
@renovate renovate bot deleted the renovate/all-minor-patch branch July 3, 2023 00:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@ArnaudBarre