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

chore(deps): update all non-major dependencies #131

Merged
merged 1 commit into from
Jul 17, 2023
Merged

chore(deps): update all non-major dependencies #131

merged 1 commit into from
Jul 17, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 17, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@playwright/test (source) ^1.35.1 -> ^1.36.1 age adoption passing confidence
@swc/core (source) ^1.3.68 -> ^1.3.69 age adoption passing confidence
@types/react (source) ^18.2.14 -> ^18.2.15 age adoption passing confidence
@types/react-dom (source) ^18.2.6 -> ^18.2.7 age adoption passing confidence
@​vitejs/release-scripts ^1.2.0 -> ^1.2.1 age adoption passing confidence
esbuild ^0.18.11 -> ^0.18.13 age adoption passing confidence
pnpm (source) 8.6.7 -> 8.6.8 age adoption passing confidence
styled-components (source) ^6.0.3 -> ^6.0.4 age adoption passing confidence
vite (source) ^4.4.2 -> ^4.4.4 age adoption passing confidence

Release Notes

Microsoft/playwright (@​playwright/test)

v1.36.1

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/24184 - [REGRESSION]: Snapshot name contains some random string after test name when tests are run in container

Browser Versions
  • Chromium 115.0.5790.75
  • Mozilla Firefox 115.0
  • WebKit 17.0

This version was also tested against the following stable channels:

  • Google Chrome 114
  • Microsoft Edge 114

v1.36.0

Compare Source

Highlights

🏝️ Summer maintenance release.

Browser Versions
  • Chromium 115.0.5790.75
  • Mozilla Firefox 115.0
  • WebKit 17.0

This version was also tested against the following stable channels:

  • Google Chrome 114
  • Microsoft Edge 114
swc-project/swc (@​swc/core)

v1.3.69

Compare Source

Bug Fixes

  • (es/compat) Visit children of while statement in the generator pass (#​7624) (d2ac2c1)

  • (es/compat) Fix loose mode of the spread pass (#​7608) (a7daa5b)

  • (es/minifier) Don't drop unused properties of top-level vars (#​7638) (19ba714)

Features
Miscellaneous Tasks
  • (es/parser) Scope use of lexical to certain features (#​7644) (a961090)
Refactor
Build
evanw/esbuild (esbuild)

v0.18.13

Compare Source

  • Add the --drop-labels= option (#​2398)

    If you want to conditionally disable some development-only code and have it not be present in the final production bundle, right now the most straightforward way of doing this is to use the --define: flag along with a specially-named global variable. For example, consider the following code:

    function main() {
  DEV && doAnExpensiveCheck()
}

    You can build this for development and production like this:

    • Development: esbuild --define:DEV=true
    • Production: esbuild --define:DEV=false

    One drawback of this approach is that the resulting code crashes if you don't provide a value for DEV with --define:. In practice this isn't that big of a problem, and there are also various ways to work around this.

    However, another approach that avoids this drawback is to use JavaScript label statements instead. That's what the --drop-labels= flag implements. For example, consider the following code:

    function main() {
  DEV: doAnExpensiveCheck()
}

    With this release, you can now build this for development and production like this:

    • Development: esbuild
    • Production: esbuild --drop-labels=DEV

    This means that code containing optional development-only checks can now be written such that it's safe to run without any additional configuration. The --drop-labels= flag takes comma-separated list of multiple label names to drop.

  • Avoid causing unhandledRejection during shutdown (#​3219)

    All pending esbuild JavaScript API calls are supposed to fail if esbuild's underlying child process is unexpectedly terminated. This can happen if SIGINT is sent to the parent node process with Ctrl+C, for example. Previously doing this could also cause an unhandled promise rejection when esbuild attempted to communicate this failure to its own child process that no longer exists. This release now swallows this communication failure, which should prevent this internal unhandled promise rejection. This change means that you can now use esbuild's JavaScript API with a custom SIGINT handler that extends the lifetime of the node process without esbuild's internals causing an early exit due to an unhandled promise rejection.

  • Update browser compatibility table scripts

    The scripts that esbuild uses to compile its internal browser compatibility table have been overhauled. Briefly:

    • Converted from JavaScript to TypeScript
    • Fixed some bugs that resulted in small changes to the table
    • Added caniuse-lite and @mdn/browser-compat-data as new data sources (replacing manually-copied information)

    This change means it's now much easier to keep esbuild's internal compatibility tables up to date. You can review the table changes here if you need to debug something about this change:

v0.18.12

Compare Source

  • Fix a panic with const enum inside parentheses (#​3205)

    This release fixes an edge case where esbuild could potentially panic if a TypeScript const enum statement was used inside of a parenthesized expression and was followed by certain other scope-related statements. Here's a minimal example that triggers this edge case:

    (() => {
  const enum E { a };
  () => E.a
})

  • Allow a newline in the middle of TypeScript export type statement (#​3225)

    Previously esbuild incorrectly rejected the following valid TypeScript code:

    export type
{ T };

export type
* as foo from 'bar';

    Code that uses a newline after export type is now allowed starting with this release.

  • Fix cross-module inlining of string enums (#​3210)

    A refactoring typo in version 0.18.9 accidentally introduced a regression with cross-module inlining of string enums when combined with computed property accesses. This regression has been fixed.

  • Rewrite .js to .ts inside packages with exports (#​3201)

    Packages with the exports field are supposed to disable node's path resolution behavior that allows you to import a file with a different extension than the one in the source code (for example, importing foo/bar to get foo/bar.js). And TypeScript has behavior where you can import a non-existent .js file and you will get the .ts file instead. Previously the presence of the exports field caused esbuild to disable all extension manipulation stuff which included both node's implicit file extension searching and TypeScript's file extension swapping. However, TypeScript appears to always apply file extension swapping even in this case. So with this release, esbuild will now rewrite .js to .ts even inside packages with exports.

  • Fix a redirect edge case in esbuild's development server (#​3208)

    The development server canonicalizes directory URLs by adding a trailing slash. For example, visiting /about redirects to /about/ if /about/index.html would be served. However, if the requested path begins with two slashes, then the redirect incorrectly turned into a protocol-relative URL. For example, visiting //about redirected to //about/ which the browser turns into http://about/. This release fixes the bug by canonicalizing the URL path when doing this redirect.

pnpm/pnpm (pnpm)

v8.6.8

Compare Source

Patch Changes

  • When the same file is appended multiple times into a tarball, the last occurrence is selected when unpacking the tarball.
  • Fixed a bug in which pnpm passed the wrong scheme to git ls-remote, causing a fallback to git+ssh and resulting in a 'host key verification failed' issue #​6805.
  • Added support for publishConfig.registry in package.json for publishing #​6775.
  • pnpm rebuild now uploads the built artifacts to the content-addressable store.
  • If a command cannot be created in .bin, the exact error message is now displayed.
  • Treat linked dependencies with a tag version type as up-to-date #​6592.
  • pnpm setup now prints more details when it cannot detect the active shell.

Our Gold Sponsors

Our Silver Sponsors
styled-components/styled-components (styled-components)

v6.0.4

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.3...v6.0.4

vitejs/vite (vite)

v4.4.4

Compare Source

v4.4.3

Compare Source

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 17, 2023
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from bde1afc to c119898 Compare July 17, 2023 10:40
@ArnaudBarre ArnaudBarre merged commit 95e9919 into main Jul 17, 2023
1 check passed
@renovate renovate bot deleted the renovate/all-minor-patch branch July 17, 2023 12:07
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