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

Merged
merged 1 commit into from
Apr 18, 2023
Merged

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

merged 1 commit into from
Apr 18, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 19, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitejs/plugin-vue (source) 4.0.0 -> 4.1.0 age adoption passing confidence
bumpp 9.0.0 -> 9.1.0 age adoption passing confidence
esbuild 0.17.11 -> 0.17.15 age adoption passing confidence
eslint (source) 8.36.0 -> 8.37.0 age adoption passing confidence
pnpm (source) 7.29.1 -> 7.30.5 age adoption passing confidence
tsx 3.12.4 -> 3.12.6 age adoption passing confidence
unbuild 1.1.2 -> 1.2.0 age adoption passing confidence
vite (source) 4.1.4 -> 4.2.1 age adoption passing confidence
vitest 0.29.2 -> 0.29.8 age adoption passing confidence

Release Notes

vitejs/vite-plugin-vue

v4.1.0

Compare Source

  • fix: avoid resolving to 2.7 compiler-sfc (cf36b3e)
antfu/bumpp

v9.1.0

Compare Source

   🚨 Breaking Changes
    View changes on GitHub
evanw/esbuild

v0.17.15

Compare Source

  • Allow keywords as type parameter names in mapped types (#​3033)

    TypeScript allows type keywords to be used as parameter names in mapped types. Previously esbuild incorrectly treated this as an error. Code that does this is now supported:

    type Foo = 'a' | 'b' | 'c'
type A = { [keyof in Foo]: number }
type B = { [infer in Foo]: number }
type C = { [readonly in Foo]: number }

  • Add annotations for re-exported modules in node (#​2486, #​3029)

    Node lets you import named imports from a CommonJS module using ESM import syntax. However, the allowed names aren't derived from the properties of the CommonJS module. Instead they are derived from an arbitrary syntax-only analysis of the CommonJS module's JavaScript AST.

    To accommodate node doing this, esbuild's ESM-to-CommonJS conversion adds a special non-executable "annotation" for node that describes the exports that node should expose in this scenario. It takes the form 0 && (module.exports = { ... }) and comes at the end of the file (0 && expr means expr is never evaluated).

    Previously esbuild didn't do this for modules re-exported using the export * from syntax. Annotations for these re-exports will now be added starting with this release:

    // Original input
export { foo } from './foo'
export * from './bar'

// Old output (with --format=cjs --platform=node)
...
0 && (module.exports = {
  foo
});

// New output (with --format=cjs --platform=node)
...
0 && (module.exports = {
  foo,
  ...require("./bar")
});

    Note that you need to specify both --format=cjs and --platform=node to get these node-specific annotations.

  • Avoid printing an unnecessary space in between a number and a . (#​3026)

    JavaScript typically requires a space in between a number token and a . token to avoid the . being interpreted as a decimal point instead of a member expression. However, this space is not required if the number token itself contains a decimal point, an exponent, or uses a base other than 10. This release of esbuild now avoids printing the unnecessary space in these cases:

    // Original input
foo(1000 .x, 0 .x, 0.1 .x, 0.0001 .x, 0xFFFF_0000_FFFF_0000 .x)

// Old output (with --minify)
foo(1e3 .x,0 .x,.1 .x,1e-4 .x,0xffff0000ffff0000 .x);

// New output (with --minify)
foo(1e3.x,0 .x,.1.x,1e-4.x,0xffff0000ffff0000.x);

  • Fix server-sent events with live reload when writing to the file system root (#​3027)

    This release fixes a bug where esbuild previously failed to emit server-sent events for live reload when outdir was the file system root, such as /. This happened because / is the only path on Unix that cannot have a trailing slash trimmed from it, which was fixed by improved path handling.

v0.17.14

Compare Source

  • Allow the TypeScript 5.0 const modifier in object type declarations (#​3021)

    The new TypeScript 5.0 const modifier was added to esbuild in version 0.17.5, and works with classes, functions, and arrow expressions. However, support for it wasn't added to object type declarations (e.g. interfaces) due to an oversight. This release adds support for these cases, so the following TypeScript 5.0 code can now be built with esbuild:

    interface Foo { <const T>(): T }
type Bar = { new <const T>(): T }

  • Implement preliminary lowering for CSS nesting (#​1945)

    Chrome has implemented the new CSS nesting specification in version 112, which is currently in beta but will become stable very soon. So CSS nesting is now a part of the web platform!

    This release of esbuild can now transform nested CSS syntax into non-nested CSS syntax for older browsers. The transformation relies on the :is() pseudo-class in many cases, so the transformation is only guaranteed to work when targeting browsers that support :is() (e.g. Chrome 88+). You'll need to set esbuild's target to the browsers you intend to support to tell esbuild to do this transformation. You will get a warning if you use CSS nesting syntax with a target which includes older browsers that don't support :is().

    The lowering transformation looks like this:

    /* Original input */
a.btn {
  color: #&#8203;333;
  &:hover { color: #&#8203;444 }
  &:active { color: #&#8203;555 }
}

/* New output (with --target=chrome88) */
a.btn {
  color: #&#8203;333;
}
a.btn:hover {
  color: #&#8203;444;
}
a.btn:active {
  color: #&#8203;555;
}

    More complex cases may generate the :is() pseudo-class:

    /* Original input */
div, p {
  .warning, .error {
    padding: 20px;
  }
}

/* New output (with --target=chrome88) */
:is(div, p) :is(.warning, .error) {
  padding: 20px;
}

    In addition, esbuild now has a special warning message for nested style rules that start with an identifier. This isn't allowed in CSS because the syntax would be ambiguous with the existing declaration syntax. The new warning message looks like this:

    ▲ [WARNING] A nested style rule cannot start with "p" because it looks like the start of a declaration [css-syntax-error]

    <stdin>:1:7:
      1 │ main { p { margin: auto } }
        │        ^
        ╵        :is(p)

  To start a nested style rule with an identifier, you need to wrap the identifier in ":is(...)" to
  prevent the rule from being parsed as a declaration.

    Keep in mind that the transformation in this release is a preliminary implementation. CSS has many features that interact in complex ways, and there may be some edge cases that don't work correctly yet.

  • Minification now removes unnecessary & CSS nesting selectors

    This release introduces the following CSS minification optimizations:

    /* Original input */
a {
  font-weight: bold;
  & {
    color: blue;
  }
  & :hover {
    text-decoration: underline;
  }
}

/* Old output (with --minify) */
a{font-weight:700;&{color:#&#8203;00f}& :hover{text-decoration:underline}}

/* New output (with --minify) */
a{font-weight:700;:hover{text-decoration:underline}color:#&#8203;00f}

  • Minification now removes duplicates from CSS selector lists

    This release introduces the following CSS minification optimization:

    /* Original input */
div, div { color: red }

/* Old output (with --minify) */
div,div{color:red}

/* New output (with --minify) */
div{color:red}

v0.17.13

Compare Source

  • Work around an issue with NODE_PATH and Go's WebAssembly internals (#​3001)

    Go's WebAssembly implementation returns EINVAL instead of ENOTDIR when using the readdir syscall on a file. This messes up esbuild's implementation of node's module resolution algorithm since encountering ENOTDIR causes esbuild to continue its search (since it's a normal condition) while other encountering other errors causes esbuild to fail with an I/O error (since it's an unexpected condition). You can encounter this issue in practice if you use node's legacy NODE_PATH feature to tell esbuild to resolve node modules in a custom directory that was not installed by npm. This release works around this problem by converting EINVAL into ENOTDIR for the readdir syscall.

  • Fix a minification bug with CSS @layer rules that have parsing errors (#​3016)

    CSS at-rules require either a {} block or a semicolon at the end. Omitting both of these causes esbuild to treat the rule as an unknown at-rule. Previous releases of esbuild had a bug that incorrectly removed unknown at-rules without any children during minification if the at-rule token matched an at-rule that esbuild can handle. Specifically cssnano can generate @layer rules with parsing errors, and empty @layer rules cannot be removed because they have side effects (@layer didn't exist when esbuild's CSS support was added, so esbuild wasn't written to handle this). This release changes esbuild to no longer discard @layer rules with parsing errors when minifying (the rule @layer c has a parsing error):

    /* Original input */
@&#8203;layer a {
  @&#8203;layer b {
    @&#8203;layer c
  }
}

/* Old output (with --minify) */
@&#8203;layer a.b;

/* New output (with --minify) */
@&#8203;layer a.b.c;

  • Unterminated strings in CSS are no longer an error

    The CSS specification provides rules for handling parsing errors. One of those rules is that user agents must close strings upon reaching the end of a line (i.e., before an unescaped line feed, carriage return or form feed character), but then drop the construct (declaration or rule) in which the string was found. For example:

    p {
  color: green;
  font-family: 'Courier New Times
  color: red;
  color: green;
}

    ...would be treated the same as:

    p { color: green; color: green; }

    ...because the second declaration (from font-family to the semicolon after color: red) is invalid and is dropped.

    Previously using this CSS with esbuild failed to build due to a syntax error, even though the code can be interpreted by a browser. With this release, the code now produces a warning instead of an error, and esbuild prints the invalid CSS such that it stays invalid in the output:

    /* esbuild's new non-minified output: */
p {
  color: green;
  font-family: 'Courier New Times
  color: red;
  color: green;
}
    /* esbuild's new minified output: */
p{font-family:'Courier New Times
color: red;color:green}

v0.17.12

Compare Source

  • Fix a crash when parsing inline TypeScript decorators (#​2991)

    Previously esbuild's TypeScript parser crashed when parsing TypeScript decorators if the definition of the decorator was inlined into the decorator itself:

    @&#8203;(function sealed(constructor: Function) {
  Object.seal(constructor);
  Object.seal(constructor.prototype);
})
class Foo {}

    This crash was not noticed earlier because this edge case did not have test coverage. The crash is fixed in this release.

eslint/eslint

v8.37.0

Compare Source

Features

Bug Fixes

  • 619f3fd fix: correctly handle null default config in RuleTester (#​17023) (Brad Zacher)
  • 1fbf118 fix: getFirstToken/getLastToken on comment-only node (#​16889) (Francesco Trotta)
  • 129e252 fix: Fix typo in logical-assignment-operators rule description (#​17000) (Francesco Trotta)

Documentation

Chores

pnpm/pnpm

v7.30.5

Compare Source

Patch Changes

  • pnpm audit should work even if there are no package.json file, just a pnpm-lock.yaml file.
  • Dedupe direct dependencies after hoisting.
  • Don't remove automatically installed peer dependencies from the root workspace project, when dedupe-peer-dependents is true #​6154.

Our Gold Sponsors

Our Silver Sponsors

v7.30.4

Compare Source

v7.30.3

Compare Source

Patch Changes

  • Should use most specific override rule when multiple rules match the same target #​6210.
  • Fix regression introduced in v7.30.1 #​6271.

Our Gold Sponsors

Our Silver Sponsors

v7.30.2

Compare Source

v7.30.1

Compare Source

Patch Changes

  • Don't write the pnpm-lock.yaml file if it has no changes and pnpm install --frozen-lockfile was executed #​6158.
  • Fix git-hosted dependencies referenced via git+ssh that use semver selectors #​6239.
  • When publish some package throws an error, the exit code should be non-zero #​5528.
  • Only three paths are displayed in pnpm audit output #​6203
  • Aliased packages should be used to resolve peer dependencies too #​4301.

Our Gold Sponsors

Our Silver Sponsors

v7.30.0

Compare Source

Minor Changes

  • Allow to set a custom directory for storing patch files via the patches-dir setting #​6215

Patch Changes

  • New directories should be prepended to NODE_PATH in command shims, not appended.
  • Retry copying file on EBUSY error #​6201.

Our Gold Sponsors

Our Silver Sponsors

v7.29.3

Compare Source

Patch Changes

  • Command shim should not set higher priority to the node_modules/.pnpm/node_modules directory through the NODE_PATH env variable, then the command's own node_modules directory #​5176.
  • extend-node-path is set back to true by default. It was set to false in v7.29.2 in order to fix issues with multiple versions of Jest in one workspace. It has caused other issues, so now we keep extending NODE_PATH. We have fixed the Jest issue with a different solution #​6213.

Our Gold Sponsors

Our Silver Sponsors

v7.29.2

Compare Source

esbuild-kit/tsx

v3.12.6

Compare Source

Bug Fixes
  • repl: suppress autocomplete transformation errors (#​205) (8e1958d)

v3.12.5

Compare Source

Bug Fixes
  • watch: ignore hidden files (afa3c78)
unjs/unbuild

v1.2.0

Compare Source

compare changes

🚀 Enhancements
  • rollup: Add jsx and tsx to esbuild loader defaults (#​198)
  • rollup: Allow regular expressions in externals array (#​145)
  • mkdist: Add new pattern option (#​139)
  • Support esbuild charset option (#​190)
  • rollup: Allow passing any all common esbuild options (8e81e2a)
  • rollup: Show size of bundled npm packages in cli output (#​243)
🩹 Fixes
  • Pass missing esbuild jsx factory options (#​224)
  • rollup: Handle array format for rollup.alias.entries option (#​220)
  • rollup: Enable interop: compat for cjs compatibility (#​215)
📖 Documentation
  • Add types to default exports (#​226)
  • Remove types field suggestion for now (e8988ae)
🏡 Chore
❤️ Contributors
vitejs/vite

v4.2.1

Compare Source

v4.2.0

Compare Source

Vite 4.2 is out!

Support env variables replacement in HTML files

Vite now supports replacing env variables in HTML files. Any properties in import.meta.env can be used in HTML files with a special %ENV_NAME% syntax:

<h1>Vite is running in %MODE%</h1>
<p>Using data from %VITE_API_URL%</p>
Sourcemaps improvements

The Chrome Dev Tools team has been working to improve the DX of Vite and Vite-powered frameworks in the dev tools. Vite 4.2 brings an improved experience and tools for framework authors to hide 3rd party code and build artifacts from the user from console log traces using server.sourcemapIgnoreList and build.rollupOptions.output.sourcemapIgnoreList.

ESM subpath imports

Vite 4.2 now supports subpath imports, thanks to @​lukeed05's resolve.exports library.

TypeScript 5 support

Vite 4.2 also supports TypeScript 5's tsconfig extends array format, thanks to tsconfck.

esbuild 0.17

esbuild v0.17.0 improved the design of its incremental, watch, and serve APIs. Check out #​11908 for the rationale of why we didn't consider the backward-incompatible changes breaking for our use cases. The updated esbuild design now allows Vite to properly cancel in-fly builds and improve server restarts.

Use Rollup types from the vite package

Expose Rollup types as a namespace. This is helpful to avoid type conflicts because of different versions of Rollup types in environments like vite-ecosystem-ci (#​12316).

import type { Rollup } from 'vite'
Português Docs Translation

The Vite documentation is now translated to Português at pt.vitejs.dev thanks to Nazaré Da Piedade .

Features
Bug Fixes

Configuration

📅 Schedule: Branch creation - "after 6pm on sunday" in timezone Asia/Shanghai, 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 10 times, most recently from f7e694b to 2e2e921 Compare March 26, 2023 04:09
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from f0df054 to bba1f0d Compare April 1, 2023 23:48
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 76499bb to 7d63773 Compare April 10, 2023 06:05
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 94be013 to 071b71b Compare April 16, 2023 23:29
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 071b71b to a42ffcd Compare April 18, 2023 00:42
@tangdaoyuan tangdaoyuan merged commit 78415a0 into main Apr 18, 2023
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
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@tangdaoyuan