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 #82

Merged
merged 1 commit into from
Apr 17, 2023
Merged

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

merged 1 commit into from
Apr 17, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 10, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@generouted/react-router ^1.11.7 -> ^1.12.6 age adoption passing confidence
@playwright/test (source) ^1.32.1 -> ^1.32.3 age adoption passing confidence
@swc/core (source) ^1.3.42 -> ^1.3.51 age adoption passing confidence
@swc/plugin-emotion ^2.5.51 -> ^2.5.59 age adoption passing confidence
@swc/plugin-styled-components ^1.5.51 -> ^1.5.59 age adoption passing confidence
@types/node (source) ^18.15.10 -> ^18.15.11 age adoption passing confidence
@types/react (source) ^18.0.29 -> ^18.0.35 age adoption passing confidence
esbuild ^0.17.14 -> ^0.17.17 age adoption passing confidence
react-router-dom ^6.9.0 -> ^6.10.0 age adoption passing confidence
typescript (source) ^5.0.2 -> ^5.0.4 age adoption passing confidence

Release Notes

oedotme/generouted

v1.12.6

Compare Source

Commits

Changelog: oedotme/generouted@v1.12.5...v1.12.6

v1.12.5

Compare Source

Commits

Changelog: oedotme/generouted@v1.12.4...v1.12.5

v1.12.4

Compare Source

Commits

Changelog: oedotme/generouted@v1.12.3...v1.12.4

v1.12.3

Compare Source

Changes

New generouted explorer - interactive playground for file-based routing.

You can run it online via StackBlitz

Open in StackBlitz

Commits

Changelog: oedotme/generouted@v1.12.2...v1.12.3

v1.12.2

Compare Source

Commits

Changelog: oedotme/generouted@v1.12.1...v1.12.2

v1.12.1

Compare Source

Commits

Changelog: oedotme/generouted@v1.12.0...v1.12.1

v1.12.0

Compare Source

Changes

The integrations updated are generouted/react-router and generouted/solid-router. Now each integration is bundled and exported via its package namespace that was used originally only for the plugin and internal client exports.

Upgrading

The setup should be easier now, only one package to install and use @generouted/react-router or @generouted/solid-router. Installing the generouted package manually is no longer necessary:

-pnpm add @​generouted/react-router generouted react-router-dom
+pnpm add @​generouted/react-router react-router-dom

The plugin is now accessible via /plugin and the Routes via the package index:

-import generouted from '@​generouted/react-router'
+import generouted from '@​generouted/react-router/plugin'

-import { Routes } from 'generouted/react-router'
+import { Routes } from '@​generouted/react-router'

Same applies to the @generouted/solid-router integration.

Commits

Changelog: oedotme/generouted@v1.11.7...v1.12.0

Microsoft/playwright

v1.32.3

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/22144 - [BUG] WebServer only starting after timeouthttps://github.com/microsoft/playwright/pull/221911 - chore: allow reusing browser between the testshttps://github.com/microsoft/playwright/issues/222155 - [BUG] Tests failing in toPass often marked as passed

Browser Versions

  • Chromium 112.0.5615.29
  • Mozilla Firefox 111.0
  • WebKit 16.4

This version was also tested against the following stable channels:

  • Google Chrome 111
  • Microsoft Edge 111

v1.32.2

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/21993 - [BUG] Browser crash when using Playwright VSC extension and trace-viewer enabled in confighttps://github.com/microsoft/playwright/issues/220033 - [Feature] Make Vue component mount props less restrictivhttps://github.com/microsoft/playwright/issues/2208989 - [REGRESSION]: Tests failing with "Error: tracing.stopChunk"

Browser Versions

  • Chromium 112.0.5615.29
  • Mozilla Firefox 111.0
  • WebKit 16.4

This version was also tested against the following stable channels:

  • Google Chrome 111
  • Microsoft Edge 111
swc-project/swc

v1.3.51

Compare Source

Bug Fixes
Features
  • (es/modules) Use function instead of arrow function unconditionally (#​7273) (5d3313a)
Miscellaneous Tasks
Refactor
Build

v1.3.50

Compare Source

Bug Fixes

  • (es) Fix a crash related to an empty source map (#​7229) (c665918)

  • (es/codegen) Respect ascii_only for identifiers (#​7247) (e35097f)

  • (es/compat) Handle export function in reserved_word (#​7251) (2e947e7)

  • (es/minifier) Fix handling of optional chaining when hoist_props is enabled (#​7246) (a44fea1)

  • (es/parser) Use a hard error for missing r-paren in an if stmt (#​7223) (b1c40a4)

  • (es/parser) Reset ctx for cond while parsing a stmt (#​7232) (01db30f)

  • (es/parser) Parse const type parameters in arrow function expressions (#​7242) (6614886)

Features
Refactor
Testing
Build

v1.3.49

Compare Source

Features
Refactor

v1.3.47

Compare Source

Bug Fixes
Features
Refactor
  • (macros/ast-node) Drop darling to reduce compile time (#​7214) (3f61638)

v1.3.46

Compare Source

v1.3.45

Compare Source

Bug Fixes
Features
Testing

v1.3.44

Compare Source

Bug Fixes
Documentation
Features
Miscellaneous Tasks
  • (cargo) Refactor Cargo.toml to reduce merge conflict (#​7139) (2826198)
Refactor
Build
evanw/esbuild

v0.17.17

Compare Source

  • Fix CSS nesting transform for top-level & (#​3052)

    Previously esbuild could crash with a stack overflow when lowering CSS nesting rules with a top-level &, such as in the code below. This happened because esbuild's CSS nesting transform didn't handle top-level &, causing esbuild to inline the top-level selector into itself. This release handles top-level & by replacing it with the :scope pseudo-class:

    /* Original code */
&,
a {
  .b {
    color: red;
  }
}

/* New output (with --target=chrome90) */
:is(:scope, a) .b {
  color: red;
}

  • Support exports in package.json for extends in tsconfig.json (#​3058)

    TypeScript 5.0 added the ability to use extends in tsconfig.json to reference a path in a package whose package.json file contains an exports map that points to the correct location. This doesn't automatically work in esbuild because tsconfig.json affects esbuild's path resolution, so esbuild's normal path resolution logic doesn't apply.

    This release adds support for doing this by adding some additional code that attempts to resolve the extends path using the exports field. The behavior should be similar enough to esbuild's main path resolution logic to work as expected.

    Note that esbuild always treats this extends import as a require() import since that's what TypeScript appears to do. Specifically the require condition will be active and the import condition will be inactive.

  • Fix watch mode with NODE_PATH (#​3062)

    Node has a rarely-used feature where you can extend the set of directories that node searches for packages using the NODE_PATH environment variable. While esbuild supports this too, previously a bug prevented esbuild's watch mode from picking up changes to imported files that were contained directly in a NODE_PATH directory. You're supposed to use NODE_PATH for packages, but some people abuse this feature by putting files in that directory instead (e.g. node_modules/some-file.js instead of node_modules/some-pkg/some-file.js). The watch mode bug happens when you do this because esbuild first tries to read some-file.js as a directory and then as a file. Watch mode was incorrectly waiting for some-file.js to become a valid directory. This release fixes this edge case bug by changing watch mode to watch some-file.js as a file when this happens.

v0.17.16

Compare Source

  • Fix CSS nesting transform for triple-nested rules that start with a combinator (#​3046)

    This release fixes a bug with esbuild where triple-nested CSS rules that start with a combinator were not transformed correctly for older browsers. Here's an example of such a case before and after this bug fix:

    /* Original input */
.a {
  color: red;
  > .b {
    color: green;
    > .c {
      color: blue;
    }
  }
}

/* Old output (with --target=chrome90) */
.a {
  color: red;
}
.a > .b {
  color: green;
}
.a .b > .c {
  color: blue;
}

/* New output (with --target=chrome90) */
.a {
  color: red;
}
.a > .b {
  color: green;
}
.a > .b > .c {
  color: blue;
}

  • Support --inject with a file loaded using the copy loader (#​3041)

    This release now allows you to use --inject with a file that is loaded using the copy loader. The copy loader copies the imported file to the output directory verbatim and rewrites the path in the import statement to point to the copied output file. When used with --inject, this means the injected file will be copied to the output directory as-is and a bare import statement for that file will be inserted in any non-copy output files that esbuild generates.

    Note that since esbuild doesn't parse the contents of copied files, esbuild will not expose any of the export names as usable imports when you do this (in the way that esbuild's --inject feature is typically used). However, any side-effects that the injected file has will still occur.

v0.17.15

Compare Source

  • Allow keywords as type parameter names in mapped types (#​3033)

    TypeScript allows type keywords to be used as parameter names in mapped types. Previously esbuild incorrectly treated this as an error. Code that does this is now supported:

    type Foo = 'a' | 'b' | 'c'
type A = { [keyof in Foo]: number }
type B = { [infer in Foo]: number }
type C = { [readonly in Foo]: number }

  • Add annotations for re-exported modules in node (#​2486, #​3029)

    Node lets you import named imports from a CommonJS module using ESM import syntax. However, the allowed names aren't derived from the properties of the CommonJS module. Instead they are derived from an arbitrary syntax-only analysis of the CommonJS module's JavaScript AST.

    To accommodate node doing this, esbuild's ESM-to-CommonJS conversion adds a special non-executable "annotation" for node that describes the exports that node should expose in this scenario. It takes the form 0 && (module.exports = { ... }) and comes at the end of the file (0 && expr means expr is never evaluated).

    Previously esbuild didn't do this for modules re-exported using the export * from syntax. Annotations for these re-exports will now be added starting with this release:

    // Original input
export { foo } from './foo'
export * from './bar'

// Old output (with --format=cjs --platform=node)
...
0 && (module.exports = {
  foo
});

// New output (with --format=cjs --platform=node)
...
0 && (module.exports = {
  foo,
  ...require("./bar")
});

    Note that you need to specify both --format=cjs and --platform=node to get these node-specific annotations.

  • Avoid printing an unnecessary space in between a number and a . (#​3026)

    JavaScript typically requires a space in between a number token and a . token to avoid the . being interpreted as a decimal point instead of a member expression. However, this space is not required if the number token itself contains a decimal point, an exponent, or uses a base other than 10. This release of esbuild now avoids printing the unnecessary space in these cases:

    // Original input
foo(1000 .x, 0 .x, 0.1 .x, 0.0001 .x, 0xFFFF_0000_FFFF_0000 .x)

// Old output (with --minify)
foo(1e3 .x,0 .x,.1 .x,1e-4 .x,0xffff0000ffff0000 .x);

// New output (with --minify)
foo(1e3.x,0 .x,.1.x,1e-4.x,0xffff0000ffff0000.x);

  • Fix server-sent events with live reload when writing to the file system root (#​3027)

    This release fixes a bug where esbuild previously failed to emit server-sent events for live reload when outdir was the file system root, such as /. This happened because / is the only path on Unix that cannot have a trailing slash trimmed from it, which was fixed by improved path handling.

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
Microsoft/TypeScript

v5.0.4: TypeScript 5.0.4

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

v5.0.3: TypeScript 5.0.3

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 3am 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 Apr 10, 2023
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from 079c062 to fae94b6 Compare April 16, 2023 23:18
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from fae94b6 to 2be890c Compare April 17, 2023 09:49
@ArnaudBarre ArnaudBarre merged commit a1bfc31 into main Apr 17, 2023
@renovate renovate bot deleted the renovate/all-minor-patch branch April 17, 2023 09:52
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