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.

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

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

Merged
merged 3 commits into from
May 9, 2024
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 6, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@astrojs/check (source) ^0.5.10 -> ^0.6.0 age adoption passing confidence
@astrojs/compiler (source) ^2.7.1 -> ^2.8.0 age adoption passing confidence
@playwright/test (source) 1.43.1 -> 1.44.0 age adoption passing confidence
@playwright/test (source) ^1.43.1 -> ^1.44.0 age adoption passing confidence
@types/chai (source) ^4.3.14 -> ^4.3.16 age adoption passing confidence
@types/diff (source) ^5.2.0 -> ^5.2.1 age adoption passing confidence
@types/hast (source) ^3.0.3 -> ^3.0.4 age adoption passing confidence
@types/markdown-it (source) ^14.0.1 -> ^14.1.1 age adoption passing confidence
@types/prismjs (source) 1.26.3 -> 1.26.4 age adoption passing confidence
@types/react (source) ^18.2.79 -> ^18.3.1 age adoption passing confidence
@types/react-dom (source) ^18.2.25 -> ^18.3.0 age adoption passing confidence
@vercel/nft ^0.26.4 -> ^0.26.5 age adoption passing confidence
@vue/compiler-sfc (source) ^3.4.26 -> ^3.4.27 age adoption passing confidence
drizzle-orm (source) ^0.30.9 -> ^0.30.10 age adoption passing confidence
esbuild ^0.20.2 -> ^0.21.1 age adoption passing confidence
eslint (source) ^9.1.1 -> ^9.2.0 age adoption passing confidence
memfs ^4.9.1 -> ^4.9.2 age adoption passing confidence
preact (source) ^10.20.2 -> ^10.21.0 age adoption passing confidence
react (source) ^18.3.0 -> ^18.3.1 age adoption passing confidence
react-dom (source) ^18.3.0 -> ^18.3.1 age adoption passing confidence
rollup (source) ^4.17.1 -> ^4.17.2 age adoption passing confidence
sass ^1.75.0 -> ^1.77.0 age adoption passing confidence
semver ^7.6.0 -> ^7.6.1 age adoption passing confidence
shiki (source) ^1.3.0 -> ^1.5.0 age adoption passing confidence
svelte (source) ^4.2.15 -> ^4.2.16 age adoption passing confidence
svelte2tsx (source) ^0.7.7 -> ^0.7.8 age adoption passing confidence
tar ^7.0.1 -> ^7.1.0 age adoption passing confidence
vite (source) ^5.2.10 -> ^5.2.11 age adoption passing confidence
vue (source) ^3.4.26 -> ^3.4.27 age adoption passing confidence
zod (source) ^3.23.5 -> ^3.23.8 age adoption passing confidence

Release Notes

withastro/language-tools (@​astrojs/check)

v0.6.0

Compare Source

Minor Changes
  • 65d3425: Upgrades the language server to use Volar 2.2. This changes should have no negative impacts on the experience.
Patch Changes
withastro/compiler (@​astrojs/compiler)

v2.8.0

Compare Source

Minor Changes
  • 17f8932: The WASM binaries for the compiler are now built using Go 1.22.
Patch Changes
  • e8b6cdf: Skips printing createAstro code if the Astro global is not referenced
  • ecd7e90: Skips printing async for component functions if await is not used
microsoft/playwright (@​playwright/test)

v1.44.0

Compare Source

New APIs

Accessibility assertions

  • expect(locator).toHaveAccessibleName() checks if the element has the specified accessible name:

    const locator = page.getByRole('button');
    await expect(locator).toHaveAccessibleName('Submit');
  • expect(locator).toHaveAccessibleDescription() checks if the element has the specified accessible description:

    const locator = page.getByRole('button');
    await expect(locator).toHaveAccessibleDescription('Upload a photo');
  • expect(locator).toHaveRole() checks if the element has the specified ARIA role:

    const locator = page.getByTestId('save-button');
    await expect(locator).toHaveRole('button');

Locator handler

  • After executing the handler added with page.addLocatorHandler(), Playwright will now wait until the overlay that triggered the handler is not visible anymore. You can opt-out of this behavior with the new noWaitAfter option.
  • You can use new times option in page.addLocatorHandler() to specify maximum number of times the handler should be run.
  • The handler in page.addLocatorHandler() now accepts the locator as argument.
  • New page.removeLocatorHandler() method for removing previously added locator handlers.
const locator = page.getByText('This interstitial covers the button');
await page.addLocatorHandler(locator, async overlay => {
  await overlay.locator('#close').click();
}, { times: 3, noWaitAfter: true });
// Run your tests that can be interrupted by the overlay.
// ...
await page.removeLocatorHandler(locator);

Miscellaneous options

  • multipart option in apiRequestContext.fetch() now accepts FormData and supports repeating fields with the same name.

    const formData = new FormData();
    formData.append('file', new File(['let x = 2024;'], 'f1.js', { type: 'text/javascript' }));
    formData.append('file', new File(['hello'], 'f2.txt', { type: 'text/plain' }));
    context.request.post('https://example.com/uploadFiles', {
      multipart: formData
    });
  • expect(callback).toPass({ intervals }) can now be configured by expect.toPass.inervals option globally in testConfig.expect or per project in testProject.expect.

  • expect(page).toHaveURL(url) now supports ignoreCase option.

  • testProject.ignoreSnapshots allows to configure per project whether to skip screenshot expectations.

Reporter API

  • New method suite.entries() returns child test suites and test cases in their declaration order. suite.type and testCase.type can be used to tell apart test cases and suites in the list.
  • Blob reporter now allows overriding report file path with a single option outputFile. The same option can also be specified as PLAYWRIGHT_BLOB_OUTPUT_FILE environment variable that might be more convenient on CI/CD.
  • JUnit reporter now supports includeProjectInTestName option.

Command line

  • --last-failed CLI option for running only tests that failed in the previous run.

    First run all tests:

    $ npx playwright test
    
    Running 103 tests using 5 workers
    ...
    2 failed
      [chromium] › my-test.spec.ts:8:5 › two ─────────────────────────────────────────────────────────
      [chromium] › my-test.spec.ts:13:5 › three ──────────────────────────────────────────────────────
    101 passed (30.0s)

    Now fix the failing tests and run Playwright again with --last-failed option:

    $ npx playwright test --last-failed
    
    Running 2 tests using 2 workers
      2 passed (1.2s)

Browser Versions

  • Chromium 125.0.6422.14
  • Mozilla Firefox 125.0.1
  • WebKit 17.4

This version was also tested against the following stable channels:

  • Google Chrome 124
  • Microsoft Edge 124
vercel/nft (@​vercel/nft)

v0.26.5

Compare Source

Bug Fixes
  • Add special case for Serial Port binary (.node) modules (#​415) (e001d05)
vuejs/core (@​vue/compiler-sfc)

v3.4.27

Compare Source

Bug Fixes
drizzle-team/drizzle-orm (drizzle-orm)

v0.30.10

Compare Source

New Features
🎉 .if() function added to all WHERE expressions
Select all users after cursors if a cursor value was provided
async function someFunction(categories: string[] = [], views = 0) {
  await db
    .select()
    .from(users)
    .where(
       and(
          gt(posts.views, views).if(views > 100),
          inArray(posts.category, categories).if(categories.length > 0),
       ),
    );
}
Bug Fixes
  • Fixed internal mappings for sessions .all, .values, .execute functions in AWS DataAPI
evanw/esbuild (esbuild)

v0.21.1

Compare Source

  • Fix a regression with --keep-names (#​3756)

    The previous release introduced a regression with the --keep-names setting and object literals with get/set accessor methods, in which case the generated code contained syntax errors. This release fixes the regression:

    // Original code
    x = { get y() {} }
    
    // Output from version 0.21.0 (with --keep-names)
    x = { get y: /* @​__PURE__ */ __name(function() {
    }, "y") };
    
    // Output from this version (with --keep-names)
    x = { get y() {
    } };

v0.21.0

Compare Source

This release doesn't contain any deliberately-breaking changes. However, it contains a very complex new feature and while all of esbuild's tests pass, I would not be surprised if an important edge case turns out to be broken. So I'm releasing this as a breaking change release to avoid causing any trouble. As usual, make sure to test your code when you upgrade.

  • Implement the JavaScript decorators proposal (#​104)

    With this release, esbuild now contains an implementation of the upcoming JavaScript decorators proposal. This is the same feature that shipped in TypeScript 5.0 and has been highly-requested on esbuild's issue tracker. You can read more about them in that blog post and in this other (now slightly outdated) extensive blog post here: https://2ality.com/2022/10/javascript-decorators.html. Here's a quick example:

    const log = (fn, context) => function() {
      console.log(`before ${context.name}`)
      const it = fn.apply(this, arguments)
      console.log(`after ${context.name}`)
      return it
    }
    
    class Foo {
      @​log static foo() {
        console.log('in foo')
      }
    }
    
    // Logs "before foo", "in foo", "after foo"
    Foo.foo()

    Note that this feature is different than the existing "TypeScript experimental decorators" feature that esbuild already implements. It uses similar syntax but behaves very differently, and the two are not compatible (although it's sometimes possible to write decorators that work with both). TypeScript experimental decorators will still be supported by esbuild going forward as they have been around for a long time, are very widely used, and let you do certain things that are not possible with JavaScript decorators (such as decorating function parameters). By default esbuild will parse and transform JavaScript decorators, but you can tell esbuild to parse and transform TypeScript experimental decorators instead by setting "experimentalDecorators": true in your tsconfig.json file.

    Probably at least half of the work for this feature went into creating a test suite that exercises many of the proposal's edge cases: https://github.com/evanw/decorator-tests. It has given me a reasonable level of confidence that esbuild's initial implementation is acceptable. However, I don't have access to a significant sample of real code that uses JavaScript decorators. If you're currently using JavaScript decorators in a real code base, please try out esbuild's implementation and let me know if anything seems off.

    ⚠️ WARNING ⚠️

    This proposal has been in the works for a very long time (work began around 10 years ago in 2014) and it is finally getting close to becoming part of the JavaScript language. However, it's still a work in progress and isn't a part of JavaScript yet, so keep in mind that any code that uses JavaScript decorators may need to be updated as the feature continues to evolve. The decorators proposal is pretty close to its final form but it can and likely will undergo some small behavioral adjustments before it ends up becoming a part of the standard. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.

  • Optimize the generated code for private methods

    Previously when lowering private methods for old browsers, esbuild would generate one WeakSet for each private method. This mirrors similar logic for generating one WeakSet for each private field. Using a separate WeakMap for private fields is necessary as their assignment can be observable:

    let it
    class Bar {
      constructor() {
        it = this
      }
    }
    class Foo extends Bar {
      #x = 1
      #y = null.foo
      static check() {
        console.log(#x in it, #y in it)
      }
    }
    try { new Foo } catch {}
    Foo.check()

    This prints true false because this partially-initialized instance has #x but not #y. In other words, it's not true that all class instances will always have all of their private fields. However, the assignment of private methods to a class instance is not observable. In other words, it's true that all class instances will always have all of their private methods. This means esbuild can lower private methods into code where all methods share a single WeakSet, which is smaller, faster, and uses less memory. Other JavaScript processing tools such as the TypeScript compiler already make this optimization. Here's what this change looks like:

    // Original code
    class Foo {
      #x() { return this.#x() }
      #y() { return this.#y() }
      #z() { return this.#z() }
    }
    
    // Old output (--supported:class-private-method=false)
    var _x, x_fn, _y, y_fn, _z, z_fn;
    class Foo {
      constructor() {
        __privateAdd(this, _x);
        __privateAdd(this, _y);
        __privateAdd(this, _z);
      }
    }
    _x = new WeakSet();
    x_fn = function() {
      return __privateMethod(this, _x, x_fn).call(this);
    };
    _y = new WeakSet();
    y_fn = function() {
      return __privateMethod(this, _y, y_fn).call(this);
    };
    _z = new WeakSet();
    z_fn = function() {
      return __privateMethod(this, _z, z_fn).call(this);
    };
    
    // New output (--supported:class-private-method=false)
    var _Foo_instances, x_fn, y_fn, z_fn;
    class Foo {
      constructor() {
        __privateAdd(this, _Foo_instances);
      }
    }
    _Foo_instances = new WeakSet();
    x_fn = function() {
      return __privateMethod(this, _Foo_instances, x_fn).call(this);
    };
    y_fn = function() {
      return __privateMethod(this, _Foo_instances, y_fn).call(this);
    };
    z_fn = function() {
      return __privateMethod(this, _Foo_instances, z_fn).call(this);
    };
  • Fix an obscure bug with lowering class members with computed property keys

    When class members that use newer syntax features are transformed for older target environments, they sometimes need to be relocated. However, care must be taken to not reorder any side effects caused by computed property keys. For example, the following code must evaluate a() then b() then c():

    class Foo {
      [a()]() {}
      [b()];
      static { c() }
    }

    Previously esbuild did this by shifting the computed property key forward to the next spot in the evaluation order. Classes evaluate all computed keys first and then all static class elements, so if the last computed key needs to be shifted, esbuild previously inserted a static block at start of the class body, ensuring it came before all other static class elements:

    var _a;
    class Foo {
      constructor() {
        __publicField(this, _a);
      }
      static {
        _a = b();
      }
      [a()]() {
      }
      static {
        c();
      }
    }

    However, this could cause esbuild to accidentally generate a syntax error if the computed property key contains code that isn't allowed in a static block, such as an await expression. With this release, esbuild fixes this problem by shifting the computed property key backward to the previous spot in the evaluation order instead, which may push it into the extends clause or even before the class itself:

    // Original code
    class Foo {
      [a()]() {}
      [await b()];
      static { c() }
    }
    
    // Old output (with --supported:class-field=false)
    var _a;
    class Foo {
      constructor() {
        __publicField(this, _a);
      }
      static {
        _a = await b();
      }
      [a()]() {
      }
      static {
        c();
      }
    }
    
    // New output (with --supported:class-field=false)
    var _a, _b;
    class Foo {
      constructor() {
        __publicField(this, _a);
      }
      [(_b = a(), _a = await b(), _b)]() {
      }
      static {
        c();
      }
    }
  • Fix some --keep-names edge cases

    The NamedEvaluation syntax-directed operation in the JavaScript specification gives certain anonymous expressions a name property depending on where they are in the syntax tree. For example, the following initializers convey a name value:

    var foo = function() {}
    var bar = class {}
    console.log(foo.name, bar.name)

    When you enable esbuild's --keep-names setting, esbuild generates additional code to represent this NamedEvaluation operation so that the value of the name property persists even when the identifiers are renamed (e.g. due to minification).

    However, I recently learned that esbuild's implementation of NamedEvaluation is missing a few cases. Specifically esbuild was missing property definitions, class initializers, logical-assignment operators. These cases should now all be handled:

    var obj = { foo: function() {} }
    class Foo0 { foo = function() {} }
    class Foo1 { static foo = function() {} }
    class Foo2 { accessor foo = function() {} }
    class Foo3 { static accessor foo = function() {} }
    foo ||= function() {}
    foo &&= function() {}
    foo ??= function() {}
eslint/eslint (eslint)

v9.2.0

Compare Source

streamich/memfs (memfs)

v4.9.2

Compare Source

Bug Fixes
preactjs/preact (preact)

v10.21.0

Compare Source

Features

Fixes

Types

Maintenance

rollup/rollup (rollup)

v4.17.2

Compare Source

2024-04-30

Bug Fixes
  • Fix tree-shaking problems when using spread arguments (#​5503)
Pull Requests
sass/dart-sass (sass)

v1.77.0

Compare Source

  • Don't throw errors for at-rules in keyframe blocks.

v1.76.0

Compare Source

  • Throw errors for misplaced statements in keyframe blocks.

  • Mixins and functions whose names begin with -- are now deprecated for
    forwards-compatibility with the in-progress CSS functions and mixins spec.
    This deprecation is named css-function-mixin.

npm/node-semver (semver)

v7.6.1

Compare Source

Bug Fixes
Dependencies
Chores
shikijs/shiki (shiki)

v1.5.0

Compare Source

   🚀 Features
    View changes on GitHub

v1.4.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
sveltejs/svelte (svelte)

v4.2.16

Compare Source

Patch Changes
  • fix: check if svelte component exists on custom element destroy (#​11489)
sveltejs/language-tools (svelte2tsx)

v0.7.8

Compare Source

  • fix: rework bindable types strategy (#​2361)
isaacs/node-tar (tar)

v7.1.0

Compare Source

vitejs/vite (vite)

v5.2.11

Compare Source

colinhacks/zod (zod)

v3.23.8

Compare Source

Commits:

v3.23.7

Compare Source

v3.23.6

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 May 6, 2024
Copy link

changeset-bot bot commented May 6, 2024

⚠️ No Changeset found

Latest commit: cc58261

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions github-actions bot added feat: markdown Related to Markdown (scope) pkg: svelte Related to Svelte (scope) pkg: vue Related to Vue (scope) pkg: react Related to React (scope) pkg: preact Related to Preact (scope) pkg: lit Related to Lit (scope) pkg: integration Related to any renderer integration (scope) pkg: astro Related to the core `astro` package (scope) labels May 6, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from d402bba to 03d2e2b Compare May 7, 2024 11:01
@renovate renovate bot changed the title fix(deps): update all non-major dependencies chore(deps): update all non-major dependencies May 7, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from be6ec4f to 1a2aa8c Compare May 8, 2024 14:51
@github-actions github-actions bot added the pkg: solid Related to Solid (scope) label May 8, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 1a2aa8c to d896f8f Compare May 8, 2024 19:48
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d896f8f to 438ac4c Compare May 9, 2024 02:07
@github-actions github-actions bot added the pkg: example Related to an example package (scope) label May 9, 2024
@bluwy bluwy merged commit f9b6f4f into main May 9, 2024
14 checks passed
@bluwy bluwy deleted the renovate/all-minor-patch branch May 9, 2024 07:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file feat: markdown Related to Markdown (scope) pkg: astro Related to the core `astro` package (scope) pkg: example Related to an example package (scope) pkg: integration Related to any renderer integration (scope) pkg: lit Related to Lit (scope) pkg: preact Related to Preact (scope) pkg: react Related to React (scope) pkg: solid Related to Solid (scope) pkg: svelte Related to Svelte (scope) pkg: vue Related to Vue (scope)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant