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

Merged
merged 1 commit into from
Sep 18, 2023
Merged

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

merged 1 commit into from
Sep 18, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 18, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@playwright/test (source) ^1.37.1 -> ^1.38.0 age adoption passing confidence
@swc/core (source) ^1.3.83 -> ^1.3.85 age adoption passing confidence
@swc/plugin-emotion ^2.5.77 -> ^2.5.83 age adoption passing confidence
@swc/plugin-styled-components ^1.5.77 -> ^1.5.83 age adoption passing confidence
@types/fs-extra (source) ^11.0.1 -> ^11.0.2 age adoption passing confidence
@types/node (source) ^18.17.15 -> ^18.17.17 age adoption passing confidence
@​vitejs/release-scripts ^1.3.0 -> ^1.3.1 age adoption passing confidence
esbuild ^0.19.2 -> ^0.19.3 age adoption passing confidence
pnpm (source) 8.7.4 -> 8.7.6 age adoption passing confidence
react-router-dom ^6.15.0 -> ^6.16.0 age adoption passing confidence
styled-components (source) ^6.0.7 -> ^6.0.8 age adoption passing confidence

Release Notes

Microsoft/playwright (@​playwright/test)

v1.38.0

Compare Source

UI Mode Updates

Playwright UI Mode

  1. Zoom into time range.
  2. Network panel redesign.

New APIs

  • [browserContext.on('weberror')][browserContext.on('weberror')]
  • [locator.pressSequentially()][locator.pressSequentially()]
  • The [reporter.onEnd()][reporter.onEnd()] now reports startTime and total run duration.

Deprecations

  • The following methods were deprecated: [page.type()][page.type()], [frame.type()][frame.type()], [locator.type()][locator.type()] and [elementHandle.type()][elementHandle.type()].
    Please use [locator.fill()][locator.fill()] instead which is much faster. Use [locator.pressSequentially()][locator.pressSequentially()] only if there is a
    special keyboard handling on the page, and you need to press keys one-by-one.

Breaking Changes: Playwright no longer downloads browsers automatically

[!NOTE]
If you are using @playwright/test package, this change does not affect you.

Playwright recommends to use @playwright/test package and download browsers via npx playwright install command. If you are following this recommendation, nothing has changed for you.

However, up to v1.38, installing the playwright package instead of @playwright/test did automatically download browsers. This is no longer the case, and we recommend to explicitly download browsers via npx playwright install command.

v1.37 and earlier

playwright package was downloading browsers during npm install, while @playwright/test was not.

v1.38 and later

playwright and @playwright/test packages do not download browsers during npm install.

Recommended migration

Run npx playwright install to download browsers after npm install. For example, in your CI configuration:

- run: npm ci
- run: npx playwright install --with-deps

Alternative migration option - not recommended

Add @playwright/browser-chromium, @playwright/browser-firefox and @playwright/browser-webkit as a dependency. These packages download respective browsers during npm install. Make sure you keep the version of all playwright packages in sync:

// package.json
{
  "devDependencies": {
    "playwright": "1.38.0",
    "@​playwright/browser-chromium": "1.38.0",
    "@​playwright/browser-firefox": "1.38.0",
    "@​playwright/browser-webkit": "1.38.0"
  }
}
Browser Versions
  • Chromium 117.0.5938.62
  • Mozilla Firefox 117.0
  • WebKit 17.0

This version was also tested against the following stable channels:

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

v1.3.85

Compare Source

Bug Fixes

  • (css/modules) Support composes when using multiple subclass selectors (#​7949) (05ca19b)

  • (es/compat) Handle single expression case in static block (#​7944) (a80aec4)

  • (es/minifier) Parse a file as a module only if opts.module is true (#​7943) (b87ac64)

Features

  • (es/compat) Support pure_getters for optional_chaining (#​7933) (c091c5e)

  • (es/module) Add an option to make resolver fully resolve index.js (#​7945) (7e8d72d)

v1.3.84

Compare Source

Bug Fixes
evanw/esbuild (esbuild)

v0.19.3

Compare Source

  • Fix list-style-type with the local-css loader (#​3325)

    The local-css loader incorrectly treated all identifiers provided to list-style-type as a custom local identifier. That included identifiers such as none which have special meaning in CSS, and which should not be treated as custom local identifiers. This release fixes this bug:

    /* Original code */
ul { list-style-type: none }

/* Old output (with --loader=local-css) */
ul {
  list-style-type: stdin_none;
}

/* New output (with --loader=local-css) */
ul {
  list-style-type: none;
}

    Note that this bug only affected code using the local-css loader. It did not affect code using the css loader.

  • Avoid inserting temporary variables before use strict (#​3322)

    This release fixes a bug where esbuild could incorrectly insert automatically-generated temporary variables before use strict directives:

    // Original code
function foo() {
  'use strict'
  a.b?.c()
}

// Old output (with --target=es6)
function foo() {
  var _a;
  "use strict";
  (_a = a.b) == null ? void 0 : _a.c();
}

// New output (with --target=es6)
function foo() {
  "use strict";
  var _a;
  (_a = a.b) == null ? void 0 : _a.c();
}

  • Adjust TypeScript enum output to better approximate tsc (#​3329)

    TypeScript enum values can be either number literals or string literals. Numbers create a bidirectional mapping between the name and the value but strings only create a unidirectional mapping from the name to the value. When the enum value is neither a number literal nor a string literal, TypeScript and esbuild both default to treating it as a number:

    // Original TypeScript code
declare const foo: any
enum Foo {
  NUMBER = 1,
  STRING = 'a',
  OTHER = foo,
}

// Compiled JavaScript code (from "tsc")
var Foo;
(function (Foo) {
  Foo[Foo["NUMBER"] = 1] = "NUMBER";
  Foo["STRING"] = "a";
  Foo[Foo["OTHER"] = foo] = "OTHER";
})(Foo || (Foo = {}));

    However, TypeScript does constant folding slightly differently than esbuild. For example, it may consider template literals to be string literals in some cases:

    // Original TypeScript code
declare const foo = 'foo'
enum Foo {
  PRESENT = `${foo}`,
  MISSING = `${bar}`,
}

// Compiled JavaScript code (from "tsc")
var Foo;
(function (Foo) {
  Foo["PRESENT"] = "foo";
  Foo[Foo["MISSING"] = `${bar}`] = "MISSING";
})(Foo || (Foo = {}));

    The template literal initializer for PRESENT is treated as a string while the template literal initializer for MISSING is treated as a number. Previously esbuild treated both of these cases as a number but starting with this release, esbuild will now treat both of these cases as a string. This doesn't exactly match the behavior of tsc but in the case where the behavior diverges tsc reports a compile error, so this seems like acceptible behavior for esbuild. Note that handling these cases completely correctly would require esbuild to parse type declarations (see the declare keyword), which esbuild deliberately doesn't do.

  • Ignore case in CSS in more places (#​3316)

    This release makes esbuild's CSS support more case-agnostic, which better matches how browsers work. For example:

    /* Original code */
@​KeyFrames Foo { From { OpaCity: 0 } To { OpaCity: 1 } }
body { CoLoR: YeLLoW }

/* Old output (with --minify) */
@​KeyFrames Foo{From {OpaCity: 0} To {OpaCity: 1}}body{CoLoR:YeLLoW}

/* New output (with --minify) */
@​KeyFrames Foo{0%{OpaCity:0}To{OpaCity:1}}body{CoLoR:#ff0}

    Please never actually write code like this.

  • Improve the error message for null entries in exports (#​3377)

    Package authors can disable package export paths with the exports map in package.json. With this release, esbuild now has a clearer error message that points to the null token in package.json itself instead of to the surrounding context. Here is an example of the new error message:

    ✘ [ERROR] Could not resolve "msw/browser"

    lib/msw-config.ts:2:28:
      2 │ import { setupWorker } from 'msw/browser';
        ╵                             ~~~~~~~~~~~~~

  The path "./browser" cannot be imported from package "msw" because it was explicitly disabled by
  the package author here:

    node_modules/msw/package.json:17:14:
      17 │       "node": null,
         ╵               ~~~~

  You can mark the path "msw/browser" as external to exclude it from the bundle, which will remove
  this error and leave the unresolved path in the bundle.

  • Parse and print the with keyword in import statements

    JavaScript was going to have a feature called "import assertions" that adds an assert keyword to import statements. It looked like this:

    import stuff from './stuff.json' assert { type: 'json' }

    The feature provided a way to assert that the imported file is of a certain type (but was not allowed to affect how the import is interpreted, even though that's how everyone expected it to behave). The feature was fully specified and then actually implemented and shipped in Chrome before the people behind the feature realized that they should allow it to affect how the import is interpreted after all. So import assertions are no longer going to be added to the language.

    Instead, the current proposal is to add a feature called "import attributes" instead that adds a with keyword to import statements. It looks like this:

    import stuff from './stuff.json' with { type: 'json' }

    This feature provides a way to affect how the import is interpreted. With this release, esbuild now has preliminary support for parsing and printing this new with keyword. The with keyword is not yet interpreted by esbuild, however, so bundling code with it will generate a build error. All this release does is allow you to use esbuild to process code containing it (such as removing types from TypeScript code). Note that this syntax is not yet a part of JavaScript and may be removed or altered in the future if the specification changes (which it already has once, as described above). If that happens, esbuild reserves the right to remove or alter its support for this syntax too.

pnpm/pnpm (pnpm)

v8.7.6

Compare Source

Patch Changes

  • Don't run the prepublishOnly scripts of git-hosted dependencies #​7026.
  • Fix a bug in which use-node-version or node-version isn't passed down to checkEngine when using pnpm workspace, resulting in an error #​6981.
  • Don't print out each deprecated subdependency separately with its deprecation message. Just print out a summary of all the deprecated subdependencies #​6707.
  • Fixed an ENOENT error that was sometimes happening during install with "hoisted" node_modules #​6756.

Our Gold Sponsors

Our Silver Sponsors

v8.7.5

Compare Source

Patch Changes

  • Improve performance of installation by using a worker for creating the symlinks inside node_modules/.pnpm #​7069.
  • Tarballs that have hard links are now unpacked successfully. This fixes a regression introduced in v8.7.0, which was shipped with our new in-house tarball parser #​7062.

Our Gold Sponsors

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

v6.16.0

Compare Source

Minor Changes
Patch Changes
  • Properly encode rendered URIs in server rendering to avoid hydration errors (#​10769)
styled-components/styled-components (styled-components)

v6.0.8

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.7...v6.0.8

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 Sep 18, 2023
@ArnaudBarre ArnaudBarre merged commit de5993e into main Sep 18, 2023
1 check passed
@ArnaudBarre ArnaudBarre deleted the renovate/all-minor-patch branch September 18, 2023 08:13
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