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

Merged
merged 2 commits into from
Jan 26, 2024
Merged

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

merged 2 commits into from
Jan 26, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 20, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@emotion/react (source) ^11.11.1 -> ^11.11.3 age adoption passing confidence
@generouted/react-router ^1.16.1 -> ^1.18.2 age adoption passing confidence
@playwright/test (source) ^1.39.0 -> ^1.41.1 age adoption passing confidence
@swc/core (source) ^1.3.96 -> ^1.3.106 age adoption passing confidence
@swc/plugin-emotion ^2.5.98 -> ^2.5.115 age adoption passing confidence
@swc/plugin-styled-components ^1.5.98 -> ^1.5.115 age adoption passing confidence
@types/node (source) ^20.9.0 -> ^20.11.7 age adoption passing confidence
@types/react (source) ^18.2.37 -> ^18.2.48 age adoption passing confidence
@types/react-dom (source) ^18.2.15 -> ^18.2.18 age adoption passing confidence
@types/styled-components (source) ^5.1.30 -> ^5.1.34 age adoption passing confidence
esbuild ^0.19.5 -> ^0.19.12 age adoption passing confidence
fs-extra ^11.1.1 -> ^11.2.0 age adoption passing confidence
pnpm (source) 8.10.5 -> 8.14.3 age adoption passing confidence
react-router-dom (source) ^6.18.0 -> ^6.21.3 age adoption passing confidence
styled-components (source) ^6.1.1 -> ^6.1.8 age adoption passing confidence
typescript (source) ^5.2.2 -> ^5.3.3 age adoption passing confidence
vite (source) ^5.0.2 -> ^5.0.12 age adoption passing confidence

Release Notes

emotion-js/emotion (@​emotion/react)

v11.11.3

Compare Source

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

v1.18.2

Compare Source

Commits

Changelog: oedotme/generouted@v1.18.1...v1.18.2

v1.18.1

Compare Source

Commits

Changelog: oedotme/generouted@v1.18.0...v1.18.1

v1.18.0

Compare Source

Commits

Changelog: oedotme/generouted@v1.17.1...v1.18.0

v1.17.1

Compare Source

Commits

Changelog: oedotme/generouted@v1.17.0...v1.17.1

v1.17.0

Compare Source

Breaking changes — Solid integration ONLY
  • @generouted/solid-router v1.17.0 now requires using @solidjs/router v0.10.1
  • <Outlet /> component was removed from @solidjs/router, you'll need to use {props.children} instead
// src/pages/_app.tsx

// import { Outlet } from '@&#8203;solidjs/router'
import { ParentProps, Show } from 'solid-js'

export default function App(props: ParentProps) {
  // return <main><Outlet /></main>
  return <main>{props.children}</main>
}
// src/pages/posts/_layout.tsx

// import { Outlet } from '@&#8203;solidjs/router'
import { ParentProps, Show } from 'solid-js'

export default function PostsLayout(props: ParentProps) {
  // return <section><Outlet /></section>
  return <section>{props.children}</section>
}

Commits

Changelog: oedotme/generouted@v1.16.1...v1.17.0

microsoft/playwright (@​playwright/test)

v1.41.1

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/29067 - [REGRESSION] Codegen/Recorder: not all clicks are being actioned nor recordedhttps://github.com/microsoft/playwright/issues/290288 - [REGRESSION] React component tests throw type error when passing null/undefined to componenhttps://github.com/microsoft/playwright/issues/2902727 - [REGRESSION] React component tests not passing Date prop valuhttps://github.com/microsoft/playwright/issues/29023023 - [REGRESSION] React component tests not rendering children phttps://github.com/microsoft/playwright/issues/290199019 - [REGRESSION] trace.playwright.dev does not currently support the loading from URL

Browser Versions

  • Chromium 121.0.6167.57
  • Mozilla Firefox 121.0
  • WebKit 17.4

This version was also tested against the following stable channels:

  • Google Chrome 120
  • Microsoft Edge 120

v1.41.0

Compare Source

New APIs

Browser Versions

  • Chromium 121.0.6167.57
  • Mozilla Firefox 121.0
  • WebKit 17.4

This version was also tested against the following stable channels:

  • Google Chrome 120
  • Microsoft Edge 120

v1.40.1

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/28319 - [REGRESSION]: Version 1.40.0 Produces corrupted traceshttps://github.com/microsoft/playwright/issues/283711 - [BUG] The color of the 'ok' text did not change to green in the vs code test results sectiohttps://github.com/microsoft/playwright/issues/2832121 - [BUG] Ambiguous test outcome and status for serial mohttps://github.com/microsoft/playwright/issues/28362362 - [BUG] Merging blobs ends up in Error: Cannot create a string longer than 0x1fffffe8 characthttps://github.com/microsoft/playwright/pull/282398239 - fix: collect all errors in removeFolders

Browser Versions
  • Chromium 120.0.6099.28
  • Mozilla Firefox 119.0
  • WebKit 17.4

This version was also tested against the following stable channels:

  • Google Chrome 119
  • Microsoft Edge 119

v1.40.0

Compare Source

Test Generator Update

Playwright Test Generator

New tools to generate assertions:

Here is an example of a generated test with assertions:

import { test, expect } from '@&#8203;playwright/test';

test('test', async ({ page }) => {
  await page.goto('https://playwright.dev/');
  await page.getByRole('link', { name: 'Get started' }).click();
  await expect(page.getByLabel('Breadcrumbs').getByRole('list')).toContainText('Installation');
  await expect(page.getByLabel('Search')).toBeVisible();
  await page.getByLabel('Search').click();
  await page.getByPlaceholder('Search docs').fill('locator');
  await expect(page.getByPlaceholder('Search docs')).toHaveValue('locator');
});

New APIs

Other Changes

Browser Versions

  • Chromium 120.0.6099.28
  • Mozilla Firefox 119.0
  • WebKit 17.4

This version was also tested against the following stable channels:

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

v1.3.106

Compare Source

Bug Fixes
Features
Miscellaneous Tasks

v1.3.105

Compare Source

Bug Fixes
Miscellaneous Tasks
Testing

v1.3.104

Compare Source

Bug Fixes

v1.3.103

Compare Source

Bug Fixes
Documentation
Features
  • (html/parser) Allow self-closing /> on non-void HTML elements via a flag (#​8460) (566063d)
Refactor
Testing

v1.3.102

Compare Source

Bug Fixes

v1.3.101

Compare Source

v1.3.100

Compare Source

Bug Fixes
Miscellaneous Tasks
Build

v1.3.99

Compare Source

evanw/esbuild (esbuild)

v0.19.12

Compare Source

  • The "preserve" JSX mode now preserves JSX text verbatim (#​3605)

    The JSX specification deliberately doesn't specify how JSX text is supposed to be interpreted and there is no canonical way to interpret JSX text. Two most popular interpretations are Babel and TypeScript. Yes they are different (esbuild deliberately follows TypeScript by the way).

    Previously esbuild normalized text to the TypeScript interpretation when the "preserve" JSX mode is active. However, "preserve" should arguably reproduce the original JSX text verbatim so that whatever JSX transform runs after esbuild is free to interpret it however it wants. So with this release, esbuild will now pass JSX text through unmodified:

    // Original code
let el =
  <a href={'/'} title='&apos;&quot;'> some text
    {foo}
      more text </a>

// Old output (with --loader=jsx --jsx=preserve)
let el = <a href="/" title={`'"`}>
  {" some text"}
  {foo}
  {"more text "}
</a>;

// New output (with --loader=jsx --jsx=preserve)
let el = <a href={"/"} title='&apos;&quot;'> some text
    {foo}
      more text </a>;

  • Allow JSX elements as JSX attribute values

    JSX has an obscure feature where you can use JSX elements in attribute position without surrounding them with {...}. It looks like this:

    let el = <div data-ab=<><a/><b/></>/>;

    I think I originally didn't implement it even though it's part of the JSX specification because it previously didn't work in TypeScript (and potentially also in Babel?). However, support for it was silently added in TypeScript 4.8 without me noticing and Babel has also since fixed their bugs regarding this feature. So I'm adding it to esbuild too now that I know it's widely supported.

    Keep in mind that there is some ongoing discussion about removing this feature from JSX. I agree that the syntax seems out of place (it does away with the elegance of "JSX is basically just XML with {...} escapes" for something arguably harder to read, which doesn't seem like a good trade-off), but it's in the specification and TypeScript and Babel both implement it so I'm going to have esbuild implement it too. However, I reserve the right to remove it from esbuild if it's ever removed from the specification in the future. So use it with caution.

  • Fix a bug with TypeScript type parsing (#​3574)

    This release fixes a bug with esbuild's TypeScript parser where a conditional type containing a union type that ends with an infer type that ends with a constraint could fail to parse. This was caused by the "don't parse a conditional type" flag not getting passed through the union type parser. Here's an example of valid TypeScript code that previously failed to parse correctly:

    type InferUnion<T> = T extends { a: infer U extends number } | infer U extends number ? U : never

v0.19.11

Compare Source

  • Fix TypeScript-specific class transform edge case (#​3559)

    The previous release introduced an optimization that avoided transforming super() in the class constructor for TypeScript code compiled with useDefineForClassFields set to false if all class instance fields have no initializers. The rationale was that in this case, all class instance fields are omitted in the output so no changes to the constructor are needed. However, if all of this is the case and there are #private instance fields with initializers, those private instance field initializers were still being moved into the constructor. This was problematic because they were being inserted before the call to super() (since super() is now no longer transformed in that case). This release introduces an additional optimization that avoids moving the private instance field initializers into the constructor in this edge case, which generates smaller code, matches the TypeScript compiler's output more closely, and avoids this bug:

    // Original code
class Foo extends Bar {
  #private = 1;
  public: any;
  constructor() {
    super();
  }
}

// Old output (with esbuild v0.19.9)
class Foo extends Bar {
  constructor() {
    super();
    this.#private = 1;
  }
  #private;
}

// Old output (with esbuild v0.19.10)
class Foo extends Bar {
  constructor() {
    this.#private = 1;
    super();
  }
  #private;
}

// New output
class Foo extends Bar {
  #private = 1;
  constructor() {
    super();
  }
}

  • Minifier: allow reording a primitive past a side-effect (#​3568)

    The minifier previously allowed reordering a side-effect past a primitive, but didn't handle the case of reordering a primitive past a side-effect. This additional case is now handled:

    // Original code
function f() {
  let x = false;
  let y = x;
  const boolean = y;
  let frag = $.template(`<p contenteditable="${boolean}">hello world</p>`);
  return frag;
}

// Old output (with --minify)
function f(){const e=!1;return $.template(`<p contenteditable="${e}">hello world</p>`)}

// New output (with --minify)
function f(){return $.template('<p contenteditable="false">hello world</p>')}

  • Minifier: consider properties named using known Symbol instances to be side-effect free (#​3561)

    Many things in JavaScript can have side effects including property accesses and ToString operations, so using a symbol such as Symbol.iterator as a computed property name is not obviously side-effect free. This release adds a special case for known Symbol instances so that they are considered side-effect free when used as property names. For example, this class declaration will now be considered side-effect free:

    class Foo {
  *[Symbol.iterator]() {
  }
}

  • Provide the stop() API in node to exit esbuild's child process (#​3558)

    You can now call stop() in esbuild's node API to exit esbuild's child process to reclaim the resources used. It only makes sense to do this for a long-lived node process when you know you will no longer be making any more esbuild API calls. It is not necessary to call this to allow node to exit, and it's advantageous to not call this in between calls to esbuild's API as sharing a single long-lived esbuild child process is more efficient than re-creating a new esbuild child process for every API call. This API call used to exist but was removed in version 0.9.0. This release adds it back due to a user request.

v0.19.10

Compare Source

  • Fix glob imports in TypeScript files (#​3319)

    This release fixes a problem where bundling a TypeScript file containing a glob import could emit a call to a helper function that doesn't exist. The problem happened because esbuild's TypeScript transformation removes unused imports (which is required for correctness, as they may be type-only imports) and esbuild's glob import transformation wasn't correctly marking the imported helper function as used. This wasn't caught earlier because most of esbuild's glob import tests were written in JavaScript, not in TypeScript.

  • Fix require() glob imports with bundling disabled (#​3546)

    Previously require() calls containing glob imports were incorrectly transformed when bundling was disabled. All glob imports should only be transformed when bundling is enabled. This bug has been fixed.

  • Fix a panic when transforming optional chaining with define (#​3551, #​3554)

    This release fixes a case where esbuild could crash with a panic, which was triggered by using define to replace an expression containing an optional chain. Here is an example:

    // Original code
console.log(process?.env.SHELL)

// Old output (with --define:process.env={})
/* panic: Internal error (while parsing "<stdin>") */

// New output (with --define:process.env={})
var define_process_env_default = {};
console.log(define_process_env_default.SHELL);

    This fix was contributed by @​hi-ogawa.

  • Work around a bug in node's CommonJS export name detector (#​3544)

    The export names of a CommonJS module are dynamically-determined at run time because CommonJS exports are properties on a mutable object. But the export names of an ES module are statically-determined at module instantiation time by using import and export syntax and cannot be changed at run time.

    When you import a CommonJS module into an ES module in node, node scans over the source code to attempt to detect the set of export names that the CommonJS module will end up using. That statically-determined set of names is used as the set of names that the ES module is allowed to import at module instantiation time. However, this scan appears to have bugs (or at least, can cause false positives) because it doesn't appear to do any scope analysis. Node will incorrectly consider the module to export something even if the assignment is done to a local variable instead of to the module-level exports object. For example:

    // confuseNode.js
exports.confuseNode = function(exports) {
  // If this local is called "exports", node incorrectly
  // thinks this file has an export called "notAnExport".
  exports.notAnExport = function() {
  };
};

    You can see that node incorrectly thinks the file confuseNode.js has an export called notAnExport when that file is loaded in an ES module context:

    $ node -e 'import("./confuseNode.js").then(console.log)'
[Module: null prototype] {
  confuseNode: [Function (anonymous)],
  default: { confuseNode: [Function (anonymous)] },
  notAnExport: undefined
}

    To avoid this, esbuild will now rename local variables that use the names exports and module when generating CommonJS output for the node platform.

  • Fix the return value of esbuild's super() shim (#​3538)

    Some people write constructor methods that use the return value of super() instead of using this. This isn't too common because TypeScript doesn't let you do that but it can come up when writing JavaScript. Previously esbuild's class lowering transform incorrectly transformed the return value of super() into undefined. With this release, the return value of super() will now be this instead:

    // Original code
class Foo extends Object {
  field
  constructor() {
    console.log(typeof super())
  }
}
new Foo

// Old output (with --target=es6)
class Foo extends Object {
  constructor() {
    var __super = (...args) => {
      super(...args);
      __publicField(this, "field");
    };
    console.log(typeof __super());
  }
}
new Foo();

// New output (with --target=es6)
class Foo extends Object {
  constructor() {
    var __super = (...args) => {
      super(...args);
      __publicField(this, "field");
      return this;
    };
    console.log(typeof __super());
  }
}
new Foo();

  • Terminate the Go GC when esbuild's stop() API is called (#​3552)

    If you use esbuild with WebAssembly and pass the worker: false flag to esbuild.initialize(), then esbuild will run the WebAssembly module on the main thread. If you do this within a Deno test and that test calls esbuild.stop() to clean up esbuild's resources, Deno may complain that a setTimeout() call lasted past the end of the test. This happens when the Go is in the middle of a garbage collection pass and has scheduled additional ongoing garbage collection work. Normally calling esbuild.stop() will terminate the web worker that the WebAssembly module runs in, which will terminate the Go GC, but that doesn't happen if you disable the web worker with worker: false.

    With this release, esbuild will now attempt to terminate the Go GC in this edge case by calling clearTimeout() on these pending timeouts.

  • Apply /* @&#8203;__NO_SIDE_EFFECTS__ */ on tagged template literals (#​3511)

    Tagged template literals that reference functions annotated with a @__NO_SIDE_EFFECTS__ comment are now able to be removed via tree-shaking if the result is unused. This is a convention from Rollup. Here is an example:

    // Original code
const html = /* @&#8203;__NO_SIDE_EFFECTS__ */ (a, ...b) => ({ a, b })
html`<a>remove</a>`
x = html`<b>keep</b>`

// Old output (with --tree-shaking=true)
const html = /* @&#8203;__NO_SIDE_EFFECTS__ */ (a, ...b) => ({ a, b });
html`<a>remove</a>`;
x = html`<b>keep</b>`;

// New output (with --tree-shaking=true)
const html = /* @&#8203;__NO_SIDE_EFFECTS__ */ (a, ...b) => ({ a, b });
x = html`<b>keep</b>`;

    Note that this feature currently only works within a single file, so it's not especially useful. This feature does not yet work across separate files. I still recommend using @__PURE__ annotations instead of this feature, as they have wider tooling support. The drawback of course is that @__PURE__ annotations need to be added at each call site, not at the declaration, and for non-call expressions such as template literals you need to wrap the expression in an IIFE (immediately-invoked function expression) to create a call expression to apply the @__PURE__ annotation to.

  • Publish builds for IBM AIX PowerPC 64-bit (#​3549)

    This release publishes a binary executable to npm for IBM AIX PowerPC 64-bit, which means that in theory esbuild can now be installed in that environment with npm install esbuild. This hasn't actually been tested yet. If you have access to such a system, it would be helpful to confirm whether or not doing this actually works.

v0.19.9

Compare Source

  • Add support for transforming new CSS gradient syntax for older browsers

    The specification called CSS Images Module Level 4 introduces new CSS gradient syntax for customizing how the browser interpolates colors in between color stops. You can now cont

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 Nov 20, 2023
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 15 times, most recently from dab63a8 to d75dcc8 Compare November 27, 2023 00:54
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 11 times, most recently from d6b0d14 to cab37b9 Compare December 4, 2023 12:08
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 4a95e16 to 8afca24 Compare December 6, 2023 09:20
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from 740ea4f to c2cfd62 Compare January 17, 2024 13:56
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 15 times, most recently from 994cd15 to 6957ab2 Compare January 25, 2024 07:04
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Jan 26, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

@ArnaudBarre ArnaudBarre merged commit a847abe into main Jan 26, 2024
1 check passed
@ArnaudBarre ArnaudBarre deleted the renovate/all-minor-patch branch January 26, 2024 22:06
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