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

Merged
merged 1 commit into from
Aug 19, 2024
Merged

chore(deps): update build #11651

merged 1 commit into from
Aug 19, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 19, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@swc/core (source) ^1.7.10 -> ^1.7.11 age adoption passing confidence
esbuild ^0.23.0 -> ^0.23.1 age adoption passing confidence
rollup (source) ^4.20.0 -> ^4.21.0 age adoption passing confidence
vite (source) ^5.4.0 -> ^5.4.1 age adoption passing confidence

Release Notes

swc-project/swc (@​swc/core)

v1.7.11

Compare Source

Bug Fixes
Features
  • (es/typescript) Add native_class_properties to skip reordering of class properties inits (#​9421) (d2929d1)

  • (estree/compat) Remove dependency on rayon (#​9393) (34d1b27)

  • (html/minifier) Support using custom css minifier (#​9425) (970cc81)

Miscellaneous Tasks
evanw/esbuild (esbuild)

v0.23.1

Compare Source

  • Allow using the node: import prefix with es* targets (#​3821)

    The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

    // Original code
    import fs from 'node:fs'
    fs.open
    
    // Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
    import fs from "fs";
    fs.open;
    
    // New output (with --bundle --format=esm --platform=node --target=node18,es2022)
    import fs from "node:fs";
    fs.open;
  • Fix a panic when using the CLI with invalid build flags if --analyze is present (#​3834)

    Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

  • Fix incorrect location of certain error messages (#​3845)

    This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

  • Print comments before case clauses in switch statements (#​3838)

    With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

  • Fix a memory leak with pluginData (#​3825)

    With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

rollup/rollup (rollup)

v4.21.0

Compare Source

2024-08-18

Features
  • Add option to configure directory for virtual modules when preserving modules (#​5602)
Pull Requests
vitejs/vite (vite)

v5.4.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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Aug 19, 2024
Copy link

Size Report

Bundles

File Size Gzip Brotli
runtime-dom.global.prod.js 98.7 kB 37.4 kB 33.7 kB
vue.global.prod.js 156 kB 57.2 kB 50.9 kB

Usages

Name Size Gzip Brotli
createApp 54.2 kB 21 kB 19.1 kB
createSSRApp 58.1 kB 22.6 kB 20.6 kB
defineCustomElement 58.8 kB 22.5 kB 20.5 kB
overall 67.8 kB 26 kB 23.7 kB

Copy link

pkg-pr-new bot commented Aug 19, 2024

commit: 817ec49

@vue/compiler-core

pnpm add https://pkg.pr.new/@vue/compiler-core@11651

@vue/compiler-dom

pnpm add https://pkg.pr.new/@vue/compiler-dom@11651

@vue/compiler-sfc

pnpm add https://pkg.pr.new/@vue/compiler-sfc@11651

@vue/compiler-ssr

pnpm add https://pkg.pr.new/@vue/compiler-ssr@11651

@vue/reactivity

pnpm add https://pkg.pr.new/@vue/reactivity@11651

@vue/runtime-core

pnpm add https://pkg.pr.new/@vue/runtime-core@11651

@vue/runtime-dom

pnpm add https://pkg.pr.new/@vue/runtime-dom@11651

@vue/server-renderer

pnpm add https://pkg.pr.new/@vue/server-renderer@11651

@vue/shared

pnpm add https://pkg.pr.new/@vue/shared@11651

vue

pnpm add https://pkg.pr.new/vue@11651

@vue/compat

pnpm add https://pkg.pr.new/@vue/compat@11651

Open in Stackblitz

@yyx990803 yyx990803 merged commit 4469972 into main Aug 19, 2024
15 checks passed
@yyx990803 yyx990803 deleted the renovate/build branch August 19, 2024 02:33
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant