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 build #10271

Merged
merged 1 commit into from Feb 5, 2024
Merged

chore(deps): update build #10271

merged 1 commit into from Feb 5, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 5, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@rollup/plugin-alias (source) ^5.0.1 -> ^5.1.0 age adoption passing confidence
@rollup/plugin-json (source) ^6.0.1 -> ^6.1.0 age adoption passing confidence
@rollup/plugin-replace (source) ^5.0.4 -> ^5.0.5 age adoption passing confidence
@vitejs/plugin-vue (source) ^4.4.0 -> ^4.6.2 age adoption passing confidence
esbuild ^0.19.5 -> ^0.20.0 age adoption passing confidence
rollup (source) ^4.1.4 -> ^4.9.6 age adoption passing confidence
rollup-plugin-esbuild ^6.1.0 -> ^6.1.1 age adoption passing confidence
rollup-plugin-polyfill-node ^0.12.0 -> ^0.13.0 age adoption passing confidence
terser (source) ^5.22.0 -> ^5.27.0 age adoption passing confidence
vite (source) ^5.0.0 -> ^5.0.12 age adoption passing confidence

Release Notes

rollup/plugins (@​rollup/plugin-alias)

v5.1.0

2023-11-25

Features
  • feat: add warning to avoid unintended duplicate modules (#​1634)
rollup/plugins (@​rollup/plugin-json)

v6.1.0

2023-12-12

Features
  • feat: add includeArbitraryNames option (#​1641)
rollup/plugins (@​rollup/plugin-replace)

v5.0.5

2023-10-29

Bugfixes
  • fix: prevent variable before colons from being replaced when preventAssigment is true (#​1609)
vitejs/vite-plugin-vue (@​vitejs/plugin-vue)

v4.5.0

v4.4.1

evanw/esbuild (esbuild)

v0.20.0

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.19.0 or ~0.19.0. See npm's documentation about semver for more information.

This time there is only one breaking change, and it only matters for people using Deno. Deno tests that use esbuild will now fail unless you make the change described below.

  • Work around API deprecations in Deno 1.40.x (#​3609, #​3611)

    Deno 1.40.0 was just released and introduced run-time warnings about certain APIs that esbuild uses. With this release, esbuild will work around these run-time warnings by using newer APIs if they are present and falling back to the original APIs otherwise. This should avoid the warnings without breaking compatibility with older versions of Deno.

    Unfortunately, doing this introduces a breaking change. The newer child process APIs lack a way to synchronously terminate esbuild's child process, so calling esbuild.stop() from within a Deno test is no longer sufficient to prevent Deno from failing a test that uses esbuild's API (Deno fails tests that create a child process without killing it before the test ends). To work around this, esbuild's stop() function has been changed to return a promise, and you now have to change esbuild.stop() to await esbuild.stop() in all of your Deno tests.

  • Reorder implicit file extensions within node_modules (#​3341, #​3608)

    In version 0.18.0, esbuild changed the behavior of implicit file extensions within node_modules directories (i.e. in published packages) to prefer .js over .ts even when the --resolve-extensions= order prefers .ts over .js (which it does by default). However, doing that also accidentally made esbuild prefer .css over .ts, which caused problems for people that published packages containing both TypeScript and CSS in files with the same name.

    With this release, esbuild will reorder TypeScript file extensions immediately after the last JavaScript file extensions in the implicit file extension order instead of putting them at the end of the order. Specifically the default implicit file extension order is .tsx,.ts,.jsx,.js,.css,.json which used to become .jsx,.js,.css,.json,.tsx,.ts in node_modules directories. With this release it will now become .jsx,.js,.tsx,.ts,.css,.json instead.

    Why even rewrite the implicit file extension order at all? One reason is because the .js file is more likely to behave correctly than the .ts file. The behavior of the .ts file may depend on tsconfig.json and the tsconfig.json file may not even be published, or may use extends to refer to a base tsconfig.json file that wasn't published. People can get into this situation when they forget to add all .ts files to their .npmignore file before publishing to npm. Picking .js over .ts helps make it more likely that resulting bundle will behave correctly.

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.

rollup/rollup (rollup)

v4.9.6

Compare Source

2024-01-21

Bug Fixes
  • Detect side effects when an element that was pushed into an array is modified via the array (#​5352)
Pull Requests

v4.9.5

Compare Source

2024-01-12

Bug Fixes
  • Fix issue where on Windows, Rollup would not load due to problems with the MSVC executable (#​5335)
Pull Requests

v4.9.4

Compare Source

2024-01-06

Bug Fixes
  • Use quotes for keys in namespaces that are only numbers but are not valid integers (#​5328)
  • Allow to have comments between pure annotations and the annoted node (#​5332)
Pull Requests

v4.9.3

Compare Source

2024-01-05

Bug Fixes
  • Support __proto__ as export/import name (#​5313)
  • Use ESTree AST type over custom type in user-facing types (#​5323)
Pull Requests

v4.9.2

Compare Source

2023-12-30

Bug Fixes
  • Extend support for arbitrary namespace identifiers in SystemJS (#​5321)
  • Do not wrongly flag functions without side effects as side effects if moduleSideEffects is false (#​5322)
Pull Requests

v4.9.1

Compare Source

2023-12-17

Bug Fixes
  • Fix an issue where break statements could include the wrong label (#​5297)
Pull Requests

v4.9.0

Compare Source

2023-12-13

Features
  • Fully support arbitrary strings as import and export identifiers (#​5298)
Pull Requests

v4.8.0

Compare Source

2023-12-11

Features
  • Improve experimentalMinChunkSize to take already loaded modules from dynamic imports into account (#​5294)
Pull Requests

v4.7.0

Compare Source

2023-12-08

Features
  • Add build for Linux riscv64 architecture (#​5288)
Bug Fixes
  • Improve error message when native Windows build does not start (#​5284)
Pull Requests

v4.6.1

Compare Source

2023-11-30

Bug Fixes
  • Resolve a situation where declaring the same var several times was considered a conflict (#​5276)
Pull Requests

v4.6.0

Compare Source

2023-11-26

Features
  • Allow this.addWatchFile in all plugin hooks (#​5270)
Bug Fixes
  • Show helpful error when native binaries are not installed due to an npm issue (#​5267)
  • Do not access this context in this.addWatchFile so it does not need to be bound when passed around (#​5270)
Pull Requests

v4.5.2

Compare Source

2023-11-24

Bug Fixes
  • Handle files with UTF-8 BOM when using the commonjs plugin (#​5268)
Pull Requests

v4.5.1

Compare Source

2023-11-21

Bug Fixes
  • Do not error when a function expression uses the same name for a parameter and its id (#​5262)
Pull Requests

v4.5.0

Compare Source

2023-11-18

Bug Fixes
  • Show a proper error when using native Rollup on armv7 musl Linux (#​5255)
Pull Requests
egoist/rollup-plugin-esbuild (rollup-plugin-esbuild)

v6.1.1

Compare Source

Bug Fixes
FredKSchott/rollup-plugin-polyfill-node (rollup-plugin-polyfill-node)

v0.13.0

Compare Source

terser/terser (terser)

v5.27.0

Compare Source

  • Created minify_sync() alternative to minify() since there's no async code left.

v5.26.0

Compare Source

  • Do not take the /*#__PURE__*/ annotation into account when the side_effects compress option is off.
  • The preserve_annotations option now automatically opts annotation comments in, instead of requiring the comments option to be configured for this.
  • Refuse to parse empty parenthesized expressions (())

v5.25.0

Compare Source

  • Regex properties added to reserved property mangler (#​1471)
  • pure_new option added to drop unused new expressions.

v5.24.0

Compare Source

  • Improve formatting performance in V8 by keeping a small work string and a large output string

v5.23.0

Compare Source

  • When top_retain will keep a variable assignment around, inline the assignee when it's shorter than the name (#​1434)
  • Remove empty class static {} blocks.
vitejs/vite (vite)

v5.0.12

Compare Source

Please refer to CHANGELOG.md for details.

v5.0.11

Compare Source

v5.0.10

Compare Source

v5.0.9

Compare Source

v5.0.8

Compare Source

v5.0.7

Compare Source

v5.0.6

Compare Source

v5.0.5

Compare Source

v5.0.4

Compare Source

v5.0.3

Compare Source

v5.0.2

Compare Source

v5.0.1

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 Feb 5, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Feb 5, 2024

Size Report

Bundles

File Size Gzip Brotli
runtime-dom.global.prod.js 91.2 kB (+995 B) 34.9 kB (+534 B) 31.3 kB (+405 B)
vue.global.prod.js 153 kB (+6.26 kB) 56 kB (+2.44 kB) 49.6 kB (+1.79 kB)

Usages

Name Size Gzip Brotli
createApp 51.4 kB (+1.03 kB) 20.2 kB (+544 B) 18.4 kB (+420 B)
createSSRApp 54.7 kB (+1.03 kB) 21.5 kB (+533 B) 19.6 kB (+413 B)
defineCustomElement 53.6 kB (+1.03 kB) 21 kB (+546 B) 19 kB (+416 B)
overall 65.1 kB (+1.03 kB) 25.3 kB (+532 B) 22.9 kB (+449 B)

@netlify Netlify
Copy link

netlify bot commented Feb 5, 2024

❌ Deploy Preview for vue-sfc-playground failed.

Name Link
🔨 Latest commit 74902a1
🔍 Latest deploy log https://app.netlify.com/sites/vue-sfc-playground/deploys/65c0576fd1d3ad00086fdb4f

@yyx990803 yyx990803 merged commit dbc4677 into main Feb 5, 2024
11 of 15 checks passed
@yyx990803 yyx990803 deleted the renovate/build branch February 5, 2024 03:37
@yyx990803
Copy link
Member

@rollup/plugin-replace 5.0.5 seems to have caused the custom enum inlining to fail, leading to bigger bundle size.

@yyx990803
Copy link
Member

This is indeed a regression in @rollup/plugin-replace: rollup/plugins#1619

Pinning to 5.0.4 for now.

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.

None yet
1 participant
@yyx990803