Skip to content

Update dependency happy-dom to v18 #74

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 15, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
happy-dom 17.6.3 -> 18.0.1 age adoption passing confidence

Release Notes

capricorn86/happy-dom (happy-dom)

v18.0.1

Compare Source

👷‍♂️ Patch fixes
  • Addresses an issue where an error occurred if the Element ID was set to the same name as a Window property with a null value - By @​capricorn86 in task #​1841

v18.0.0

Compare Source

💣 Breaking Changes
  • Makes the types for Happy DOM strict - By @​capricorn86 in task #​1154
    • This makes it possible to use the option skipLibCheck set to "false" in the typescript configuration for projects with a strict configuration
    • This change has resulted in that some types has changed and is therefore considered as a breaking change
  • BrowserContext.close() now throws an error when trying to close the default context of a browser - By @​capricorn86 in task #​1154
🎨 Features

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Jun 15, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nuxt/test-utils@3.19.1
npm error Found: happy-dom@18.0.1
npm error node_modules/happy-dom
npm error   dev happy-dom@"18.0.1" from the root project
npm error   peerOptional happy-dom@"*" from vitest@3.2.3
npm error   node_modules/vitest
npm error     dev vitest@"3.2.3" from the root project
npm error     peerOptional vitest@"^0.34.6 || ^1.0.0 || ^2.0.0 || ^3.0.0" from @nuxt/test-utils@3.19.1
npm error     node_modules/@nuxt/test-utils
npm error       dev @nuxt/test-utils@"3.19.1" from the root project
npm error       1 more (vitest-environment-nuxt)
npm error
npm error Could not resolve dependency:
npm error peerOptional happy-dom@"^9.10.9 || ^10.0.0 || ^11.0.0 || ^12.0.0 || ^13.0.0 || ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0" from @nuxt/test-utils@3.19.1
npm error node_modules/@nuxt/test-utils
npm error   dev @nuxt/test-utils@"3.19.1" from the root project
npm error   @nuxt/test-utils@">=3.13.1" from vitest-environment-nuxt@1.0.1
npm error   node_modules/vitest-environment-nuxt
npm error     vitest-environment-nuxt@"^1.0.1" from @nuxt/test-utils@3.19.1
npm error
npm error Conflicting peer dependency: happy-dom@17.6.3
npm error node_modules/happy-dom
npm error   peerOptional happy-dom@"^9.10.9 || ^10.0.0 || ^11.0.0 || ^12.0.0 || ^13.0.0 || ^14.0.0 || ^15.0.0 || ^16.0.0 || ^17.0.0" from @nuxt/test-utils@3.19.1
npm error   node_modules/@nuxt/test-utils
npm error     dev @nuxt/test-utils@"3.19.1" from the root project
npm error     @nuxt/test-utils@">=3.13.1" from vitest-environment-nuxt@1.0.1
npm error     node_modules/vitest-environment-nuxt
npm error       vitest-environment-nuxt@"^1.0.1" from @nuxt/test-utils@3.19.1
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-06-15T14_28_44_893Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-06-15T14_28_44_893Z-debug-0.log

@renovate renovate bot had a problem deploying to microservice-ui-nuxt-js-deployment June 15, 2025 08:01 Failure
@renovate renovate bot force-pushed the renovate/major-happy-dom-monorepo branch from 45c3df8 to 456cb0c Compare June 15, 2025 14:28
@renovate renovate bot had a problem deploying to microservice-ui-nuxt-js-deployment June 15, 2025 14:28 Failure
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants