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

Merged
merged 1 commit into from
Jun 11, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 13, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@iconify-json/carbon ^1.1.32 -> ^1.1.35 age adoption passing confidence
@iconify-json/logos ^1.1.42 -> ^1.1.43 age adoption passing confidence
@playwright/test (source) ^1.44.0 -> ^1.44.1 age adoption passing confidence
@rollup/plugin-commonjs (source) ^25.0.7 -> ^25.0.8 age adoption passing confidence
@shikijs/vitepress-twoslash (source) ^1.5.1 -> ^1.6.4 age adoption passing confidence
@testing-library/dom ^9.3.3 -> ^9.3.4 age adoption passing confidence
@testing-library/vue ^8.0.3 -> ^8.1.0 age adoption passing confidence
@types/jsdom (source) ^21.1.6 -> ^21.1.7 age adoption passing confidence
@types/node (source) ^20.12.11 -> ^20.14.2 age adoption passing confidence
@unocss/reset ^0.60.0 -> ^0.60.4 age adoption passing confidence
@vitejs/plugin-vue (source) ^5.0.4 -> ^5.0.5 age adoption passing confidence
@vueuse/core (source) ^10.9.0 -> ^10.10.1 age adoption passing confidence
@wdio/protocols (source) ^8.32.0 -> ^8.38.0 age adoption passing confidence
d3-graph-controller (source) ^3.0.8 -> ^3.0.9 age adoption passing confidence
debug ^4.3.4 -> ^4.3.5 age adoption passing confidence
esbuild ^0.21.1 -> ^0.21.5 age adoption passing confidence
eslint (source) ^9.2.0 -> ^9.4.0 age adoption passing confidence
get-tsconfig ^4.7.4 -> ^4.7.5 age adoption passing confidence
happy-dom ^14.10.1 -> ^14.12.0 age adoption passing confidence
jsdom ^24.0.0 -> ^24.1.0 age adoption passing confidence
lint-staged ^15.2.2 -> ^15.2.5 age adoption passing confidence
micromatch ^4.0.5 -> ^4.0.7 age adoption passing confidence
mlly ^1.7.0 -> ^1.7.1 age adoption passing confidence
picocolors ^1.0.0 -> ^1.0.1 age adoption passing confidence
playwright (source) ^1.44.0 -> ^1.44.1 age adoption passing confidence
playwright-core (source) ^1.44.0 -> ^1.44.1 age adoption passing confidence
rimraf ^5.0.5 -> ^5.0.7 age adoption passing confidence
rollup (source) ^4.17.2 -> ^4.18.0 age adoption passing confidence
rollup-plugin-dts ^6.1.0 -> ^6.1.1 age adoption passing confidence
rollup-plugin-license ^3.3.1 -> ^3.4.0 age adoption passing confidence
tsx ^4.9.3 -> ^4.15.2 age adoption passing confidence
unocss ^0.60.0 -> ^0.60.4 age adoption passing confidence
unplugin-auto-import ^0.17.5 -> ^0.17.6 age adoption passing confidence
vite-plugin-pages ^0.32.1 -> ^0.32.2 age adoption passing confidence
vitepress (source) ^1.1.4 -> ^1.2.3 age adoption passing confidence
vue-router ^4.3.2 -> ^4.3.3 age adoption passing confidence
webdriverio (source) ^8.36.1 -> ^8.38.2 age adoption passing confidence
zx ^8.0.2 -> ^8.1.2 age adoption passing confidence

Release Notes

microsoft/playwright (@​playwright/test)

v1.44.1

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/30779 - [REGRESSION]: When using video: 'on' with VSCode extension the browser got closed
https://github.com/microsoft/playwright/issues/30755 - [REGRESSION]: Electron launch with spaces inside executablePath didn't workhttps://github.com/microsoft/playwright/issues/307700 - [REGRESSION]: Mask elements outside of viewport when creating fullscreen screenshots didn't worhttps://github.com/microsoft/playwright/issues/3085858 - [REGRESSION]: ipv6 got shown instead of localhost in show-trace/show-report

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
rollup/plugins (@​rollup/plugin-commonjs)

v25.0.8

2024-05-22

Bugfixes
  • fix: preserve the class body property keys even if they are special keywords (#​1688)
shikijs/shiki (@​shikijs/vitepress-twoslash)

v1.6.4

Compare Source

   🚀 Features
    View changes on GitHub

v1.6.3

Compare Source

   🚀 Features
    View changes on GitHub

v1.6.2

Compare Source

   🚀 Features
    View changes on GitHub

v1.6.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v1.6.0

Compare Source

   🚀 Features
    View changes on GitHub

v1.5.2

Compare Source

   🚀 Features
    View changes on GitHub
testing-library/dom-testing-library (@​testing-library/dom)

v9.3.4

Compare Source

Bug Fixes
testing-library/vue-testing-library (@​testing-library/vue)

v8.1.0

Compare Source

Features
  • Add types for props and slots in render function (d46ed8f)
unocss/unocss (@​unocss/reset)

v0.60.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.60.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
  • preset-mini: Improve performance of resolveBreakpoints  -  by @​antfu (05d90)
    View changes on GitHub

v0.60.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.60.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
vitejs/vite-plugin-vue (@​vitejs/plugin-vue)

v5.0.5

vueuse/vueuse (@​vueuse/core)

v10.10.1

Compare Source

v10.10.0

Compare Source

webdriverio/webdriverio (@​wdio/protocols)

v8.38.0

Compare Source

v8.38.0 (2024-05-24)

🚀 New Feature
🐛 Bug Fix
Committers: 4
DerYeger/yeger (d3-graph-controller)

v3.0.9

Compare Source

Patch Changes
debug-js/debug (debug)

v4.3.5

Compare Source

Patch

Thank you @​calvintwr for the fix.

evanw/esbuild (esbuild)

v0.21.5

Compare Source

  • Fix Symbol.metadata on classes without a class decorator (#​3781)

    This release fixes a bug with esbuild's support for the decorator metadata proposal. Previously esbuild only added the Symbol.metadata property to decorated classes if there was a decorator on the class element itself. However, the proposal says that the Symbol.metadata property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.

  • Allow unknown import attributes to be used with the copy loader (#​3792)

    Import attributes (the with keyword on import statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load ./bagel.js as type bagel:

    // This is an error with "--bundle" without also using "--external:./bagel.js"
    import tasty from "./bagel.js" with { type: "bagel" }

    Because of that, bundling this code with esbuild is an error unless the file ./bagel.js is external to the bundle (such as with --bundle --external:./bagel.js).

    However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the copy loader. That's because the copy loader behaves similarly to --external in that the file is left external to the bundle. The difference is that the copy loader copies the file into the output folder and rewrites the import path while --external doesn't. That means the following will now work with the copy loader (such as with --bundle --loader:.bagel=copy):

    // This is no longer an error with "--bundle" and "--loader:.bagel=copy"
    import tasty from "./tasty.bagel" with { type: "bagel" }
  • Support import attributes with glob-style imports (#​3797)

    This release adds support for import attributes (the with option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:

    async function loadLocale(locale: string): Locale {
      const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
      return unpackLocale(locale, data)
    }

    Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:

    ✘ [ERROR] No loader is configured for ".data" files: locales/en-US.data
    
        example.ts:2:28:
          2 │   const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
            ╵                             ~~~~~~~~~~~~~~~~~~~~~~~~~~
    

    In addition, this change means plugins can now access the contents of with for glob-style imports.

  • Support ${configDir} in tsconfig.json files (#​3782)

    This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence ${configDir} is now respected at the start of baseUrl and paths values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets base tsconfig.json files specified via extends refer to the directory of the top-level tsconfig.json file. Here is an example:

    {
      "compilerOptions": {
        "paths": {
          "js/*": ["${configDir}/dist/js/*"]
        }
      }
    }

    You can read more in TypeScript's blog post about their upcoming 5.5 release. Note that this feature does not make use of template literals (you need to use "${configDir}/dist/js/*" not `${configDir}/dist/js/*`). The syntax for tsconfig.json is still just JSON with comments, and JSON syntax does not allow template literals. This feature only recognizes ${configDir} in strings for certain path-like properties, and only at the beginning of the string.

  • Fix internal error with --supported:object-accessors=false (#​3794)

    This release fixes a regression in 0.21.0 where some code that was added to esbuild's internal runtime library of helper functions for JavaScript decorators fails to parse when you configure esbuild with --supported:object-accessors=false. The reason is that esbuild introduced code that does { get [name]() {} } which uses both the object-extensions feature for the [name] and the object-accessors feature for the get, but esbuild was incorrectly only checking for object-extensions and not for object-accessors. Additional tests have been added to avoid this type of issue in the future. A workaround for this issue in earlier releases is to also add --supported:object-extensions=false.

v0.21.4

Compare Source

  • Update support for import assertions and import attributes in node (#​3778)

    Import assertions (the assert keyword) have been removed from node starting in v22.0.0. So esbuild will now strip them and generate a warning with --target=node22 or above:

    ▲ [WARNING] The "assert" keyword is not supported in the configured target environment ("node22") [assert-to-with]
    
        example.mjs:1:40:
          1 │ import json from "esbuild/package.json" assert { type: "json" }
            │                                         ~~~~~~
            ╵                                         with
    
      Did you mean to use "with" instead of "assert"?
    

    Import attributes (the with keyword) have been backported to node 18 starting in v18.20.0. So esbuild will no longer strip them with --target=node18.N if N is 20 or greater.

  • Fix for await transform when a label is present

    This release fixes a bug where the for await transform, which wraps the loop in a try statement, previously failed to also move the loop's label into the try statement. This bug only affects code that uses both of these features in combination. Here's an example of some affected code:

    // Original code
    async function test() {
      outer: for await (const x of [Promise.resolve([0, 1])]) {
        for (const y of x) if (y) break outer
        throw 'fail'
      }
    }
    
    // Old output (with --target=es6)
    function test() {
      return __async(this, null, function* () {
        outer: try {
          for (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp, error; more = !(temp = yield iter.next()).done; more = false) {
            const x = temp.value;
            for (const y of x) if (y) break outer;
            throw "fail";
          }
        } catch (temp) {
          error = [temp];
        } finally {
          try {
            more && (temp = iter.return) && (yield temp.call(iter));
          } finally {
            if (error)
              throw error[0];
          }
        }
      });
    }
    
    // New output (with --target=es6)
    function test() {
      return __async(this, null, function* () {
        try {
          outer: for (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp, error; more = !(temp = yield iter.next()).done; more = false) {
            const x = temp.value;
            for (const y of x) if (y) break outer;
            throw "fail";
          }
        } catch (temp) {
          error = [temp];
        } finally {
          try {
            more && (temp = iter.return) && (yield temp.call(iter));
          } finally {
            if (error)
              throw error[0];
          }
        }
      });
    }
  • Do additional constant folding after cross-module enum inlining (#​3416, #​3425)

    This release adds a few more cases where esbuild does constant folding after cross-module enum inlining.

    // Original code: 

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 force-pushed the renovate/all-minor-patch branch 6 times, most recently from 849dc71 to 34869cc Compare May 14, 2024 10:27
@sheremet-va
Copy link
Member

Hey, @DylanPiercey Marko is behaving weird again - do you know why this happens?

Also, do you know of a good open-source project that uses Mark and Vitest? We want to move the Marko example to https://github.com/vitest-dev/vitest-ecosystem-ci from this repository.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 34869cc to 29bb0a9 Compare May 14, 2024 15:12
@DylanPiercey
Copy link
Contributor

@sheremet-va the issue happens when strange hoisting happens with multiple copies of @babel/types installed. Rebuilding a lock will usually fix it. It is something we will be fixing sometime soon.

Also currently all of the Marko vitest projects I'm aware of are internal at eBay so there isn't a good open source example at the moment. Eventually https://github.com/eBay/ebayui-core will switch to vitest and could potentially be used.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 87630b1 to e1aaaa8 Compare May 15, 2024 07:35
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 13 times, most recently from 4b7eb2e to e98aade Compare May 22, 2024 18:38
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 812802d to fad136c Compare May 23, 2024 06:58
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 21 times, most recently from 31c57e2 to 3d220d7 Compare June 9, 2024 22:33
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 00dd015 to 6295939 Compare June 11, 2024 14:32
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 6295939 to 3deb045 Compare June 11, 2024 14:57
@sheremet-va sheremet-va merged commit a06abb7 into main Jun 11, 2024
16 checks passed
@sheremet-va sheremet-va deleted the renovate/all-minor-patch branch June 11, 2024 15:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants