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 devdependencies #2593

Merged
merged 2 commits into from
Jan 1, 2024
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 1, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) ~20.10.5 -> ~20.10.6 age adoption passing confidence
esbuild ~0.19.10 -> ~0.19.11 age adoption passing confidence
eslint-plugin-jsdoc ~46.9.1 -> ~46.10.1 age adoption passing confidence
tsx ~3.13.0 -> ~3.14.0 age adoption passing confidence
vue (source) ~3.3.13 -> ~3.4.3 age adoption passing confidence

Release Notes

evanw/esbuild (esbuild)

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.

gajus/eslint-plugin-jsdoc (eslint-plugin-jsdoc)

v46.10.1

Compare Source

Bug Fixes
  • revert change to engines for now (5e6280f)

v46.10.0

Compare Source

Features
privatenumber/tsx (tsx)

v3.14.0

Compare Source

Bug Fixes
Features
  • support Node v20.6.0 module.register() & --import flag (#​337) (23e4694)

This release is also available on:

vuejs/core (vue)

v3.4.3

Compare Source

Bug Fixes
  • compiler-sfc: respect sfc parse options in cache key (b8d58ec)

v3.4.2

Compare Source

Bug Fixes

v3.4.1

Compare Source

Bug Fixes
  • compat: correct enum value for COMPILER_FILTERS feature (#​9875) (77d33e2)
  • defineModel: always default modifiers to empty object (9bc3c7e), closes #​9945
  • defineModel: support local mutation when only prop but no listener is passed (97ce041)
  • types: fix defineModel watch type error (#​9942) (4af8583), closes #​9939
Features

v3.4.0

Compare Source

Read this blog post for an overview of the release highlights.

Potential Actions Needed
  1. To fully leverage new features in 3.4, it is recommended to also update the following dependencies when upgrading to 3.4:

    • Volar / vue-tsc@^1.8.27 (required)
    • @​vitejs/plugin-vue@​^5.0.0 (if using Vite)
    • nuxt@^3.9.0 (if using Nuxt)
    • vue-loader@^17.4.0 (if using webpack or vue-cli)
  2. If using TSX with Vue, check actions needed in Removed: Global JSX Namespace.

  3. Make sure you are no longer using any deprecated features (if you are, you should have warnings in the console telling you so). They may have been removed in 3.4.

Features
Performance Improvements
  • compiler-sfc: avoid sfc source map unnecessary serialization and parsing (f15d2f6)
  • compiler-sfc: remove magic-string trim on script (e8e3ec6)
  • compiler-sfc: use faster source map addMapping (50cde7c)
  • compiler-core: optimize away isBuiltInType (66c0ed0)
  • compiler-core: optimize position cloning (2073236)
  • codegen: optimize line / column calculation during codegen (3be53d9)
  • codegen: optimize source map generation (c11002f)
  • shared: optimize makeMap (ae6fba9)
BREAKING CHANGES
Global JSX Registration Removed

Starting in 3.4, Vue no longer registers the global JSX namespace by default. This is necessary to avoid global namespace collision with React so that TSX of both libs can co-exist in the same project. This should not affect SFC-only users with latest version of Volar.

If you are using TSX, there are two options:

  1. Explicitly set jsxImportSource to 'vue' in tsconfig.json before upgrading to 3.4. You can also opt-in per file by adding a /* @&#8203;jsxImportSource vue */ comment at the top of the file.

  2. If you have code that depends on the presence of the global JSX namespace, e.g. usage of types like JSX.Element etc., you can retain the exact pre-3.4 global behavior by explicitly referencing vue/jsx, which registers the global JSX namespace.

Note that this is a type-only breaking change in a minor release, which adheres to our release policy.

Deprecated Features Removed
  • Reactivity Transform was marked deprecated in 3.3 and is now removed in 3.4. This change does not require a major due to the feature being experimental. Users who wish to continue using the feature can do so via the Vue Macros plugin.
  • app.config.unwrapInjectedRef has been removed. It was deprecated and enabled by default in 3.3. In 3.4 it is no longer possible to disable this behavior.
  • @vnodeXXX event listeners in templates are now a compiler error instead of a deprecation warning. Use @vue:XXX listeners instead.
  • v-is directive has been removed. It was deprecated in 3.3. Use the is attribute with vue: prefix instead.

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 requested a review from a team as a code owner January 1, 2024 01:48
@renovate renovate bot added the c: dependencies Pull requests that adds/updates a dependency label Jan 1, 2024
Copy link

codecov bot commented Jan 1, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (87e0490) 99.57% compared to head (c916278) 99.56%.

Additional details and impacted files
@@            Coverage Diff             @@
##             next    #2593      +/-   ##
==========================================
- Coverage   99.57%   99.56%   -0.01%     
==========================================
  Files        2807     2807              
  Lines      250401   250401              
  Branches     1142     1140       -2     
==========================================
- Hits       249336   249323      -13     
- Misses       1037     1050      +13     
  Partials       28       28              

see 2 files with indirect coverage changes

Copy link
Contributor Author

renovate bot commented Jan 1, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

@ST-DDT ST-DDT added this to the vAnytime milestone Jan 1, 2024
@ST-DDT ST-DDT self-assigned this Jan 1, 2024
@ST-DDT ST-DDT requested review from a team January 1, 2024 02:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: dependencies Pull requests that adds/updates a dependency
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants