Bump esbuild, @nuxt/module-builder, @nuxt/test-utils, nuxt and vitest by dependabot[bot] · Pull Request #2 · janu-software/nuxt-fullpage

dependabot · 2025-07-16T10:39:52Z

Bumps esbuild to 0.25.6 and updates ancestor dependencies esbuild, @nuxt/module-builder, @nuxt/test-utils, nuxt and vitest. These dependencies need to be updated together.

Updates esbuild from 0.17.19 to 0.25.6

Release notes

Sourced from esbuild's releases.

v0.25.6
Fix a memory leak when cancel() is used on a build context (#4231)

Calling rebuild() followed by cancel() in rapid succession could previously leak memory. The bundler uses a producer/consumer model internally, and the resource leak was caused by the consumer being termianted while there were still remaining unreceived results from a producer. To avoid the leak, the consumer now waits for all producers to finish before terminating.

Support empty :is() and :where() syntax in CSS (#4232)

Previously using these selectors with esbuild would generate a warning. That warning has been removed in this release for these cases.
Improve tree-shaking of try statements in dead code (#4224)

With this release, esbuild will now remove certain try statements if esbuild considers them to be within dead code (i.e. code that is known to not ever be evaluated). For example:
// Original code
return 'foo'
try { return 'bar' } catch {}
// Old output (with --minify)
return"foo";try{return"bar"}catch{}
// New output (with --minify)
return"foo";
Consider negated bigints to have no side effects

While esbuild currently considers 1, -1, and 1n to all have no side effects, it didn't previously consider -1n to have no side effects. This is because esbuild does constant folding with numbers but not bigints. However, it meant that unused negative bigint constants were not tree-shaken. With this release, esbuild will now consider these expressions to also be side-effect free:
// Original code
let a = 1, b = -1, c = 1n, d = -1n
// Old output (with --bundle --minify)
(()=>{var n=-1n;})();
// New output (with --bundle --minify)
(()=>{})();
Support a configurable delay in watch mode before rebuilding (#3476, #4178)

The watch() API now takes a delay option that lets you add a delay (in milliseconds) before rebuilding when a change is detected in watch mode. If you use a tool that regenerates multiple source files very slowly, this should make it more likely that esbuild's watch mode won't generate a broken intermediate build before the successful final build. This option is also available via the CLI using the --watch-delay= flag.

This should also help avoid confusion about the watch() API's options argument. It was previously empty to allow for future API expansion, which caused some people to think that the documentation was missing. It's no longer empty now that the watch() API has an option.

Allow mixed array for entryPoints API option (#4223)

The TypeScript type definitions now allow you to pass a mixed array of both string literals and object literals to the entryPoints API option, such as ['foo.js', { out: 'lib', in: 'bar.js' }]. This was always possible to do in JavaScript but the TypeScript type definitions were previously too restrictive.

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2023

This changelog documents all esbuild versions published in the year 2023 (versions 0.16.13 through 0.19.11).

0.19.11
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:

... (truncated)

Commits

d38c1f0 publish 0.25.6 to npm
11e547e missing ) in release notes
cc8ac0a fix trailing comment whitespace
1e3fb57 fix #4178: add the --watch-delay= option
c1f5f18 fix #4209: disable binary executable optimization on WASM platform (#4210)
3ed5ecc fix incorrect locations in CHANGELOG.md
248089c fix #4224: allow try statements to become dead
42f159c openharmony: keep makefile targets sorted
63256e1 chore: fix some comments (#4211)
d803f72 add support for openharmony-arm64 platform (#4212)
Additional commits viewable in compare view

Updates @nuxt/module-builder from 0.4.0 to 1.0.1

Release notes

Sourced from @nuxt/module-builder's releases.

v1.0.1

compare changes

📖 Documentation

Add full v1 release notes (#581, #582)

Update to latest recommendations (6b30cde)

❤️ Contributors

Daniel Roe (@danielroe)

Connor Pearson (@cjpearson)

v1.0.0

With the release of unbuild v3, the EOL status of Nuxt 2, and looking forward to Nuxt 4, we're taking the opportunity to release v1 of @nuxt/module-builder, with a range of breaking changes.

⚠️ Breaking Changes

Upgrade to unbuild v3 (#447) This major upgrade brings significant changes to the build proces but should be significantly better.

Removal of Node10 module resolution and CommonJS output (#448) As Nuxt 2 has reached EOL, we no longer generate CJS by default, and we have also removed the 'CJS bridge' feature that polyfilled __filename and __dirname.

Type errors. The module builder will now error if there are type errors when generating your runtime/* files. (Previously warnings were logged but your build would have succeeded.) Errors you receive aren't caused by the upgrade, but you might need to correct any issues before your module will build again.

🚧 Migration Guide

Replacing __filename and __dirname

We no longer polyfill these CommonJS variables. Instead, use the createResolver utility from @nuxt/kit:
import { createResolver } from '@nuxt/kit'
// Instead of __dirname and __filename
const resolver= createResolver(import.meta.url)
const runtimeDir = resolver.resolve('./runtime')
Module Resolution Changes

We no longer officially support Node10 module resolution, meaning you should remove the types/type field from your package.json. If you need to maintain compatibility with older Node.js versions or systems expecting CommonJS, you can use the typesVersions field in your package.json.

This field allows typing subpath exports (like my-module/utils) even with older moduleResolution settings. Regardless, we recommend all Nuxt users to use Bundler module resolution.
{
  "typesVersions": {
    "*": {
</tr></table> 

... (truncated)

Changelog

Sourced from @nuxt/module-builder's changelog.

v1.0.1

compare changes

📖 Documentation

Add full v1 release notes (#581, #582)

Update to latest recommendations (6b30cde)

❤️ Contributors

Daniel Roe (@danielroe)

Connor Pearson (@cjpearson)

v1.0.0

compare changes

🚀 Enhancements

⚠️ Upgrade to unbuild v3 (#447)

⚠️ Remove support for node10 resolution + cjs (#448)

build: Ignore test + story files in runtime/ directory (#480)

Add support for type exports in module re-exports (#563)

🩹 Fixes

Mark nuxi as optional peerDep (29a42ae)

Drop @nuxt/kit peer dependency & remove optionality for nuxi (5936063)

build: Handle windows path names (#399)

build: Apply resolved tsconfig to dts (#462)

Handle node10 resolution + add attw test (7309198)

Update warnings (6291cbe)

Support more than one line of type exports (0c0020f)

Split re-exports across multiple lines (7154a89)

Support star exports (8966047)

📖 Documentation

Update example build script (#359)

Update link to downloads count badge (9804e9e)(b9b27c3)

Describe configuring unbuild (#440)

🏡 Chore

Use tinyexec in test suite (7ff8ef1)

Fix links (2e57eb2)

Pin typescript until issue with vue-tsc is resolved (994135d)

Bump vue-tsc (e8cb0ef)

Bump nuxi version (5b1f00e)

... (truncated)

Commits

7a43cbf chore(release): v1.0.1
c0cac22 chore(deps): update dependency vue-sfc-transformer to ^0.1.8 (#590)
3771544 chore(deps): update pnpm to v10.8.0 (#589)
2d3daca chore(deps): lock file maintenance (#586)
36eebcd chore(deps): update dependency vue-sfc-transformer to ^0.1.5 (#585)
3dc71f9 chore(deps): update devdependency knip to ^5.47.0 (#584)
6b30cde docs: update to latest recommendations
48e98e5 docs: add full v1 release notes (#581) (#582)
aac840d chore(deps): update resolutions typescript to v5.8.3 (#579)
b0655d3 chore(release): v1.0.0
Additional commits viewable in compare view

Updates @nuxt/test-utils from 3.5.2 to 3.19.2

Release notes

Sourced from @nuxt/test-utils's releases.

v3.19.2

3.19.2 is the next patch release.

Timetable: 1 July

👉 Changelog

compare changes

🩹 Fixes

config: Add missing mocks for vue-devtools (#1321)

runtime-utils: Prevent event duplication (#1328)

config: Include tests without .nuxt. extension (#1311)

deps: Drop @nuxt/schema dependeny (fa3a99b4)

config: Use 'projects' for vitest >= v3.2 (#1344)

module: Use user vite version to merge config (#1345)

runtime-utils: Handle computed defined using an object (#1342)

🏡 Chore

Prefer nuxt over nuxi (#1310)

Pin node types (93921643)

Do not include dev-deps in engines.node calculation (2f74359b)

Add type assertions for indexed access (51b4a4e3)

Update installed-check flag (2b97d885)

✅ Tests

Update stub name for nuxt v4 (e7b07843)

Satisfy typescript (fb0dea24)

Update cucumber test for nuxt v4 welcome screen template (8ec7782f)

Simplify test (90278bac)

Update workspace example (02f9b0a0)

Make browser tests forward-compat with v4 (574ea5f9)

🤖 CI

Remove forced corepack installation (bf19bd3a)

Run knip (819aeacc)

Prepare environment before knipping (ec7d8ddd)

... (truncated)

Commits

baaecf7 v3.19.2
2b97d88 chore: update installed-check flag
574ea5f test: make browser tests forward-compat with v4
51b4a4e chore: add type assertions for indexed access
b1ff702 fix(runtime-utils): handle computed defined using an object (#1342)
5f7f980 chore(deps): update resolutions vite to v7 (#1339)
2f74359 chore: do not include dev-deps in engines.node calculation
737e133 fix(module): use user vite version to merge config (#1345)
ec7d8dd ci: prepare environment before knipping
819aeac ci: run knip
Additional commits viewable in compare view

Updates nuxt from 3.5.2 to 4.0.0

Release notes

Sourced from nuxt's releases.

v4.0.0

Nuxt 4.0 is here! 🎉

After a year of real-world testing, we're excited to announce the official release of Nuxt 4. This is a stability-focused major release, introducing a few thoughtful breaking changes in order to improve development experience.

If you've been following along, you'll recognize many of these features and changes — and if you're new to them, we hope you'll welcome them.

🔥 What's new?

Nuxt 4 is all about making your development experience smoother:

Cleaner project organization with the new app/ directory structure

Smarter data fetching - we've taken the opportunity to address some inconsistencies and improve performance with the data layer

Better TypeScript support with project-based separation between the different contexts in your project - app code, server code, shared/ folder, and configuration

Faster CLI and development with adoption of internal sockets and a faster CLI

Why these features in particular? Mostly because these kind of improvements have required making changes that are technically breaking.

In general, we aim for a hype-free approach to releases. Rather than save up features for a big release, we've been shipping improvements in Nuxt 3 minor releases.

We've also spent a lot of time figuring out how to implement these changes in a backwards-compatible way, and I hope that means that most Nuxt 3 projects can upgrade with a minimum of effort.

I'd advise reading through the upgrade guide before you start, to understand what areas of your app might be affected.

🗂️ New project structure

The biggest visible change is how projects are organized. Your application code now lives in an app/ directory by default:
my-nuxt-app/
├─ app/
│  ├─ components/
│  ├─ pages/
│  ├─ layouts/
│  └─ app.vue
├─ public/
├─ shared/
├─ server/
└─ nuxt.config.ts
This helps keep your code separate from node_modules/ and .git/, which makes file watchers faster (especially on Windows and Linux). It also gives your IDE better context about whether you're working with client or server code.

[!TIP] Don't want to migrate? That's totally fine! Nuxt will detect your existing structure and keep working exactly as before.

🎨 Updated UI templates

Nuxt’s starter templates have an all new look, with improved accessibility, default titles, and template polish (#27843).

... (truncated)

Commits

8aacdde v4.0.0
a450079 feat(nuxt): expose page routes to nitro for o11y (#32617)
97386a0 chore(deps): update all non-major dependencies (main) (#32614)
97832ab fix(nuxt): only use scrollBehaviorType for hash scrolling (#32622)
9bf809d feat(nuxt): add route announcer to default app.vue (#32621)
e35e1cc fix(nuxt)!: bump compatibilityDate to 2025-07-15
8a5309e fix(nuxt): retain old data when computed key changes (#32616)
281b559 chore(deps): update dependency @nuxt/cli to v3.26.0 (main) (#32611)
7a77637 fix(nuxt): include shared declarations in tsconfig.server.json (#32594)
6c994b4 chore(deps): update all non-major dependencies (main) (#32604)
Additional commits viewable in compare view

Updates vitest from 0.31.4 to 3.2.4

Release notes

Sourced from vitest's releases.

v3.2.4

   🐞 Bug Fixes

Use correct path for optimisation of strip-literal - by @mrginglymus in vitest-dev/vitest#8139 (44940)

Print uint and buffer as a simple string - by @sheremet-va in vitest-dev/vitest#8141 (b86bf)

browser:

Show a helpful error when spying on an export - by @sheremet-va in vitest-dev/vitest#8178 (56007)

cli:

vitest run --watch should be watch-mode - by @AriPerkkio in vitest-dev/vitest#8128 (657e8)

Use absolute path environment on Windows - by @colinaaa in vitest-dev/vitest#8105 (85dc0)

Throw error when --shard x/<count> exceeds count of test files - by @AriPerkkio in vitest-dev/vitest#8112 (8a18c)

coverage:

Ignore SCSS in browser mode - by @sheremet-va in vitest-dev/vitest#8161 (0c3be)

deps:

Update all non-major dependencies - in vitest-dev/vitest#8123 (93f32)

expect:

Handle async errors in expect.soft - by @lzl0304 in vitest-dev/vitest#8145 (68699)

pool:

Auto-adjust minWorkers when only maxWorkers specified - by @AriPerkkio in vitest-dev/vitest#8110 (14dc0)

reporter:

task.meta should be available in custom reporter's errors - by @AriPerkkio in vitest-dev/vitest#8115 (27df6)

runner:

Preserve handler wrapping on extend - by @pengooseDev in vitest-dev/vitest#8153 (a9281)

ui:

Ensure ui config option works correctly - by @lzl0304 in vitest-dev/vitest#8147 (42eeb)

    View changes on GitHub

v3.2.3

   🚀 Features

browser: Use base url instead of vitest - by @sheremet-va in vitest-dev/vitest#8126 (1d8eb)

ui: Show test annotations and metadata in the test report tab - by @sheremet-va in vitest-dev/vitest#8093 (c69be)

   🐞 Bug Fixes

Rerun tests when project's setup file is changed - by @sheremet-va in vitest-dev/vitest#8097 (0f335)

Revert expect.any return type - by @sheremet-va in vitest-dev/vitest#8129 (47514)

Run only the name plugin last, not all config plugins - by @sheremet-va in vitest-dev/vitest#8130 (83862)

pool:

Throw if user's tests use process.send() - by @AriPerkkio in vitest-dev/vitest#8125 (dfe81)

runner:

Fast sequential task updates missing - by @AriPerkkio in vitest-dev/vitest#8121 (7bd11)

Comments between fixture destructures - by @AriPerkkio in vitest-dev/vitest#8127 (dc469)

vite-node:

Unable to handle errors where sourcemap mapping empty - by @blake-newman and @hi-ogawa in vitest-dev/vitest#8071 (8aa25)

    View changes on GitHub

v3.2.2

... (truncated)

Commits

c666d14 chore: release v3.2.4
8a18c8e fix(cli): throw error when --shard x/\<count> exceeds count of test files (#...
8abd7cc chore(deps): update tinypool (#8174)
93f3200 fix(deps): update all non-major dependencies (#8123)
0c3be6f fix(coverage): ignore SCSS in browser mode (#8161)
790bc31 chore: update deprecation notice for globs (#8148)
c0eae7d chore: update deprecated workspace file log (#8118)
14dc072 fix(pool): auto-adjust minWorkers when only maxWorkers specified (#8110)
85dc019 fix(cli): use absolute path environment on Windows (#8105)
27df68a fix(reporter): task.meta should be available in custom reporter's errors (#...
Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by vitestbot, a new releaser for vitest since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [esbuild](https://github.com/evanw/esbuild) to 0.25.6 and updates ancestor dependencies [esbuild](https://github.com/evanw/esbuild), [@nuxt/module-builder](https://github.com/nuxt/module-builder), [@nuxt/test-utils](https://github.com/nuxt/test-utils), [nuxt](https://github.com/nuxt/nuxt/tree/HEAD/packages/nuxt) and [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). These dependencies need to be updated together. Updates `esbuild` from 0.17.19 to 0.25.6 - [Release notes](https://github.com/evanw/esbuild/releases) - [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG-2023.md) - [Commits](evanw/esbuild@v0.17.19...v0.25.6) Updates `@nuxt/module-builder` from 0.4.0 to 1.0.1 - [Release notes](https://github.com/nuxt/module-builder/releases) - [Changelog](https://github.com/nuxt/module-builder/blob/main/CHANGELOG.md) - [Commits](nuxt/module-builder@v0.4.0...v1.0.1) Updates `@nuxt/test-utils` from 3.5.2 to 3.19.2 - [Release notes](https://github.com/nuxt/test-utils/releases) - [Commits](nuxt/test-utils@v3.5.2...v3.19.2) Updates `nuxt` from 3.5.2 to 4.0.0 - [Release notes](https://github.com/nuxt/nuxt/releases) - [Commits](https://github.com/nuxt/nuxt/commits/v4.0.0/packages/nuxt) Updates `vitest` from 0.31.4 to 3.2.4 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v3.2.4/packages/vitest) --- updated-dependencies: - dependency-name: esbuild dependency-version: 0.25.6 dependency-type: indirect - dependency-name: "@nuxt/module-builder" dependency-version: 1.0.1 dependency-type: direct:development - dependency-name: "@nuxt/test-utils" dependency-version: 3.19.2 dependency-type: direct:development - dependency-name: nuxt dependency-version: 4.0.0 dependency-type: direct:development - dependency-name: vitest dependency-version: 3.2.4 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>

dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jul 16, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Bump esbuild, @nuxt/module-builder, @nuxt/test-utils, nuxt and vitest#2

Bump esbuild, @nuxt/module-builder, @nuxt/test-utils, nuxt and vitest#2
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/multi-c72dad040f

dependabot bot commented on behalf of github Jul 16, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

dependabot bot commented on behalf of github Jul 16, 2025

v0.25.6

Changelog: 2023

0.19.11

v1.0.1

📖 Documentation

❤️ Contributors

v1.0.0

⚠️ Breaking Changes

🚧 Migration Guide

Replacing __filename and __dirname

Module Resolution Changes

v1.0.1

📖 Documentation

❤️ Contributors

v1.0.0

🚀 Enhancements

🩹 Fixes

📖 Documentation

🏡 Chore

v3.19.2

👉 Changelog

🩹 Fixes

🏡 Chore

✅ Tests

🤖 CI

v4.0.0

🔥 What's new?

🗂️ New project structure

🎨 Updated UI templates

v3.2.4

🐞 Bug Fixes

View changes on GitHub

v3.2.3

🚀 Features

🐞 Bug Fixes

View changes on GitHub

v3.2.2

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Replacing `filename` and `dirname`