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

Merged
merged 1 commit into from
Apr 4, 2022
Merged

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

merged 1 commit into from
Apr 4, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 4, 2022

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@actions/github ^5.0.0 -> ^5.0.1 age adoption passing confidence
@happy-dom/jest-environment ^2.53.1 -> ^2.55.0 age adoption passing confidence
@storybook/addon-actions ^6.4.19 -> ^6.4.20 age adoption passing confidence
@storybook/addon-essentials ^6.4.19 -> ^6.4.20 age adoption passing confidence
@storybook/addon-links ^6.4.19 -> ^6.4.20 age adoption passing confidence
@storybook/react ^6.4.19 -> ^6.4.20 age adoption passing confidence
@unocss/reset ^0.30.8 -> ^0.30.11 age adoption passing confidence
@vitejs/plugin-react 1.2.0 -> 1.3.0 age adoption passing confidence
@vueuse/core ^8.2.3 -> ^8.2.4 age adoption passing confidence
@vueuse/integrations ^8.2.3 -> ^8.2.4 age adoption passing confidence
d3-graph-controller (source) ^2.2.20 -> ^2.2.22 age adoption passing confidence
esbuild ~0.14.28 -> ~0.14.30 age adoption passing confidence
happy-dom ^2.53.1 -> ^2.55.0 age adoption passing confidence
pnpm (source) 6.32.3 -> 6.32.4 age adoption passing confidence
prettier (source) ^2.6.1 -> ^2.6.2 age adoption passing confidence
puppeteer ^13.5.1 -> ^13.5.2 age adoption passing confidence
react-router-dom ^6.2.2 -> ^6.3.0 age adoption passing confidence
storybook-builder-vite ^0.1.22 -> ^0.1.23 age adoption passing confidence
unocss ^0.30.8 -> ^0.30.11 age adoption passing confidence
unplugin-vue2-script-setup ^0.10.1 -> ^0.10.2 age adoption passing confidence
vite ^2.8.6 -> ^2.9.1 age adoption passing confidence
vite 2.9.0-beta.9 -> 2.9.1 age adoption passing confidence
vite-plugin-ruby ^3.0.8 -> ^3.0.9 age adoption passing confidence

Release Notes

actions/toolkit

v5.0.1

capricorn86/happy-dom

v2.55.0

Compare Source

🎨 Features
  • Adds support for HTMLBaseElement. (#​429)
  • Adds support for Node.baseURI. (#​429)

v2.54.0

Compare Source

🎨 Features
  • Adds support for HTMLInputElement.setCustomValidity(), HTMLInputElement.reportValidity() and HTMLInputElement.validationMessage. (#​442)
storybookjs/storybook

v6.4.20

Compare Source

Bug Fixes
  • CLI: Fix vite/jest issue with mocked global (#​17830)
  • Angular: Fix multiple calls of Input setter (#​17633)
  • Web-components: Fix CSS class usage in CLI template (#​17702)
  • UI: Fix composition support in safari (#​17679)
  • Addon-docs: DocsPage story order should match the index (#​17669)
  • Core: Fix core.builder check (#​17606)
Maintenance
  • CLI: Add automigration to @storybook/builder-vite (#​17829)
unocss/unocss

v0.30.11

Compare Source

Bug Fixes
Features

v0.30.10

Compare Source

Bug Fixes
vitejs/vite (@​vitejs/plugin-react)

v1.3.0

vueuse/vueuse

v8.2.4

Compare Source

Bug Fixes
Features
  • useElementBounding: new options (de05a18)
DerYeger/d3-graph-controller

v2.2.22

Compare Source

Bug Fixes

v2.2.21

Compare Source

Bug Fixes
  • deps: update dependency vecti to v2.0.11 (d096471)
evanw/esbuild

v0.14.30

Compare Source

  • Change the context of TypeScript parameter decorators (#​2147)

    While TypeScript parameter decorators are expressions, they are not evaluated where they exist in the code. They are moved to after the class declaration and evaluated there instead. Specifically this TypeScript code:

    class Class {
  method(@​decorator() arg) {}
}

    becomes this JavaScript code:

    class Class {
  method(arg) {}
}
__decorate([
  __param(0, decorator())
], Class.prototype, "method", null);

    This has several consequences:

    • Whether await is allowed inside a decorator expression or not depends on whether the class declaration itself is in an async context or not. With this release, you can now use await inside a decorator expression when the class declaration is either inside an async function or is at the top-level of an ES module and top-level await is supported. Note that the TypeScript compiler currently has a bug regarding this edge case: Parameter decorators use incorrect async/await context, generated code has syntax error microsoft/TypeScript#48509.

      // Using "await" inside a decorator expression is now allowed
async function fn(foo: Promise<any>) {
  class Class {
    method(@&#8203;decorator(await foo) arg) {}
  }
  return Class
}

      Also while TypeScript currently allows await to be used like this in async functions, it doesn't currently allow yield to be used like this in generator functions. It's not yet clear whether this behavior with yield is a bug or by design, so I haven't made any changes to esbuild's handling of yield inside decorator expressions in this release.

    • Since the scope of a decorator expression is the scope enclosing the class declaration, they cannot access private identifiers. Previously this was incorrectly allowed but with this release, esbuild no longer allows this. Note that the TypeScript compiler currently has a bug regarding this edge case: Decorators broken with private fields, generated code has syntax error microsoft/TypeScript#48515.

      // Using private names inside a decorator expression is no longer allowed
class Class {
  static #priv = 123
  method(@&#8203;decorator(Class.#priv) arg) {}
}

    • Since the scope of a decorator expression is the scope enclosing the class declaration, identifiers inside parameter decorator expressions should never be resolved to a parameter of the enclosing method. Previously this could happen, which was a bug with esbuild. This bug no longer happens in this release.

      // Name collisions now resolve to the outer name instead of the inner name
let arg = 1
class Class {
  method(@&#8203;decorator(arg) arg = 2) {}
}

      Specifically previous versions of esbuild generated the following incorrect JavaScript (notice the use of arg2):

      let arg = 1;
class Class {
  method(arg2 = 2) {
  }
}
__decorateClass([
  __decorateParam(0, decorator(arg2))
], Class.prototype, "method", 1);

      This release now generates the following correct JavaScript (notice the use of arg):

      let arg = 1;
class Class {
  method(arg2 = 2) {
  }
}
__decorateClass([
  __decorateParam(0, decorator(arg))
], Class.prototype, "method", 1);

  • Fix some obscure edge cases with super property access

    This release fixes the following obscure problems with super when targeting an older JavaScript environment such as --target=es6:

    1. The compiler could previously crash when a lowered async arrow function contained a class with a field initializer that used a super property access:

      let foo = async () => class extends Object {
  bar = super.toString
}

    2. The compiler could previously generate incorrect code when a lowered async method of a derived class contained a nested class with a computed class member involving a super property access on the derived class:

      class Base {
  foo() { return 'bar' }
}
class Derived extends Base {
  async foo() {
    return new class { [super.foo()] = 'success' }
  }
}
new Derived().foo().then(obj => console.log(obj.bar))

    3. The compiler could previously generate incorrect code when a default-exported class contained a super property access inside a lowered static private class field:

      class Foo {
  static foo = 123
}
export default class extends Foo {
  static #foo = super.foo
  static bar = this.#foo
}

v0.14.29

Compare Source

  • Fix a minification bug with a double-nested if inside a label followed by else (#​2139)

    This fixes a minification bug that affects the edge case where if is followed by else and the if contains a label that contains a nested if. Normally esbuild's AST printer automatically wraps the body of a single-statement if in braces to avoid the "dangling else" if/else ambiguity common to C-like languages (where the else accidentally becomes associated with the inner if instead of the outer if). However, I was missing automatic wrapping of label statements, which did not have test coverage because they are a rarely-used feature. This release fixes the bug:

    // Original code
if (a)
  b: {
    if (c) break b
  }
else if (d)
  e()

// Old output (with --minify)
if(a)e:if(c)break e;else d&&e();

// New output (with --minify)
if(a){e:if(c)break e}else d&&e();

  • Fix edge case regarding baseUrl and paths in tsconfig.json (#​2119)

    In tsconfig.json, TypeScript forbids non-relative values inside paths if baseUrl is not present, and esbuild does too. However, TypeScript checked this after the entire tsconfig.json hierarchy was parsed while esbuild incorrectly checked this immediately when parsing the file containing the paths map. This caused incorrect warnings to be generated for tsconfig.json files that specify a baseUrl value and that inherit a paths value from an extends clause. Now esbuild will only check for non-relative paths values after the entire hierarchy has been parsed to avoid generating incorrect warnings.

  • Better handle errors where the esbuild binary executable is corrupted or missing (#​2129)

    If the esbuild binary executable is corrupted or missing, previously there was one situation where esbuild's JavaScript API could hang instead of generating an error. This release changes esbuild's library code to generate an error instead in this case.

pnpm/pnpm

v6.32.4

Compare Source

Patch Changes
  • Show a friendly error message when it is impossible to get the current Git branch name during publish #​4488.
  • When checking if the lockfile is up-to-date, an empty dependenciesMeta field in the manifest should be satisfied by a not set field in the lockfile #​4463.
  • It should be possible to reference a workspace project that has no version specified in its package.json #​4487.
prettier/prettier

v2.6.2

Compare Source

diff

Fix LESS/SCSS format error (#​12536 by @​fisker)
// Input
.background-gradient(@&#8203;cut) {
    background: linear-gradient(
        to right,
        @&#8203;white 0%,
        @&#8203;white (@&#8203;cut - 0.01%),
        @&#8203;portal-background @&#8203;cut,
        @&#8203;portal-background 100%
    );
}

// Prettier 2.6.1
TypeError: Cannot read properties of undefined (reading 'endOffset')

// Prettier 2.6.2
.background-gradient(@&#8203;cut) {
  background: linear-gradient(
    to right,
    @&#8203;white 0%,
    @&#8203;white (@&#8203;cut - 0.01%),
    @&#8203;portal-background @&#8203;cut,
    @&#8203;portal-background 100%
  );
}
Update meriyah to fix several bugs (#​12567 by @​fisker, fixes in meriyah by @​3cp)

Fixes bugs when parsing following valid code:

foo(await bar());
const regex = /.*/ms;
const element = <p>{/w/.test(s)}</p>;
class A extends B {
  #privateMethod() {
    super.method();
  }
}
puppeteer/puppeteer

v13.5.2

Compare Source

remix-run/react-router

v6.3.0

Compare Source

What's Changed

New Contributors

Full Changelog: remix-run/react-router@v6.2.2...v6.3.0

storybookjs/builder-vite

v0.1.23

Compare Source

What's Changed

Full Changelog: storybookjs/builder-vite@v0.1.22...v0.1.23

antfu/unplugin-vue2-script-setup

v0.10.2

Compare Source

Bug Fixes
  • dynamic import module to avoid breaking in browser (#​129) (33eb148)
vitejs/vite (vite)

v2.9.1

Compare Source

v2.9.0

Compare Source

Faster Cold Start

Before 2.9, the first time dev was run on a project Vite needed to perform a scan phase to discover dependencies and then pre-bundle them before starting the server. In 2.9 both scanning #​7379 and pre-bundling #​6758 of dependencies are now non-blocking, so the server starts right away during cold start. We also now allow requests to flow through the pipeline improving initial cold start load speed and increasing the chances of discovering new missing dependencies when re-processing and letting Vite populate the module graph and the browser to process files. In many cases, there is also no need to full-reload the page when new dependencies are discovered.

CSS Sourcemap support during dev (experimental)

Vite now supports CSS sourcemaps #​7173. This feature is still experimental, and it is disabled by default to avoid incurring a performance penalty for users that don't need it. To enable it, set css.devSourcemap to true.

Avoid splitting vendor chunks by default

Vite's default chunking strategy was a good fit for most SPAs, but it wasn't ideal in some other use cases. Vite doesn't have enough context to make the best decision here, so in Vite 2.9 the previous chunking strategy is now opt-in #​6534 and Vite will no longer split vendor libs in a separate chunk.

Web Workers enhancements

Web Workers now supports source map generation (see #​5417). The implementation is also now more robust, fixing several issues encountered in previous versions (#​6599).

Raw Glob Imports

Glob imports support for the raw modifier syntax has changed to using { as: 'raw' }, which works in the same way as the ?raw suffix in regular imports:

const examples = import.meta.globEager('./examples/*.html', { as: 'raw' })

The { assert: { type: 'raw' }} syntax introduced in v2.8 has been deprecated. See #​7017 for more information.

envDir changes

The envDir now correctly loads .env files in the specified directory only (defaults to root). Previously, it would load files above the directory, which imposed security issues. If you had relied on the previous behaviour, make sure you move your .env files to the correct directory, or configure the envDir option.

New tools for Plugin and Framework Authors
Client Server Communication API

Vite now provides utilities for plugins to help handle the communication with clients connected to Vite's server #​7437. Reusing the open WebSocket connection between the server and clients several use cases can be simplified (vite-plugin-inspect, SliDev, and many others). Check out the Client Server Communication docs for more information.

// Send a message from the client to the server
if (import.meta.hot) {
  import.meta.hot.send('my:from-client', { msg: 'Hey!' })
}
// And listen to client messages in a plugin
  configureServer(server) {
    server.ws.on('my:from-client', (data, client) => {
      console.log('Message from client:', data.msg) // Hey!
      // ...
    })
  }
importedCss and importedAssets to RenderedChunk type

Replace the internal chunkToEmittedCssFileMap and chunkToEmittedAssetsMap variables with public properties added by Vite to RenderedChunk objects in the renderChunk phase. These is useful for Vite-based frameworks that generate their own HTML. See #​6629.

Optimize Custom Extensions (experimental)

A new optimizeDeps.extensions: string[] option is available to enable pre-bundling of custom extensions. A respective esbuild plugin is required to handle that extension. e.g. ['.svelte', '.svelte.md']. See #​6801 for more information.

Bug Fixes

Configuration

📅 Schedule: "before 3am on Monday" (UTC).

🚦 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, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot added the dependencies label Apr 4, 2022
@netlify
Copy link

netlify bot commented Apr 4, 2022 •
edited

✅ Deploy Preview for vitest-dev ready!

Name Link
🔨 Latest commit 5e9cc94
🔍 Latest deploy log https://app.netlify.com/sites/vitest-dev/deploys/624a58fd9d14f10008514d17
😎 Deploy Preview https://deploy-preview-1094--vitest-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@antfu antfu merged commit 16684b2 into main Apr 4, 2022
@antfu antfu deleted the renovate/all-minor-patch branch April 4, 2022 02:56
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
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@antfu @renovate-bot