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 dependency happy-dom to v16 #297

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 6, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
happy-dom 15.11.7 -> 16.5.3 age adoption passing confidence

Release Notes

capricorn86/happy-dom (happy-dom)

v16.5.3

Compare Source

👷‍♂️ Patch fixes
  • Fixes problem with encoding and decoding attribute values in HTML - By @​capricorn86 in task #​1678
  • Fixes issue where it was not possible to query selector by class when the attribute value had line breaks in it - By @​capricorn86 in task #​1678

v16.5.2

Compare Source

👷‍♂️ Patch fixes
  • Event.target should be the target element after an event has been dispatched - By @​capricorn86 in task #​1529

v16.5.1

Compare Source

👷‍♂️ Patch fixes
  • Fixes issue where Comment, Text and DocumentFragment are not instances of their corresponding property on Window - By @​capricorn86 in task #​1577

v16.5.0

Compare Source

🎨 Features

v16.4.3

Compare Source

👷‍♂️ Patch fixes
  • Adds null check for if browser frame is available in Response during tear down of the Window - By @​capricorn86 in task #​1669

v16.4.2

Compare Source

👷‍♂️ Patch fixes

v16.4.1

Compare Source

👷‍♂️ Patch fixes
  • Fixes issue where HTML assigned to document.documentElement.innerHTML isnt parsed correctly since v16 - By @​capricorn86 in task #​1663

v16.4.0

Compare Source

🎨 Features

v16.3.0

Compare Source

🎨 Features
  • Adds support for child combinator to ":has()" pseudo selector (e.g. "span:has(> video)") - By @​capricorn86 in task #​1642

v16.2.9

Compare Source

👷‍♂️ Patch fixes
  • Fixes the HTMLInputElement.defaultChecked property - By @​capricorn86 in task #​1587
    • This issue caused React not to serialize the "checked" attribute correctly

v16.2.8

Compare Source

👷‍♂️ Patch fixes
  • Fixes issue where the wrong event target was used when dispatching events on HTMLFormElement or HTMLSelectElement - By @​capricorn86 in task #​1628

v16.2.7

Compare Source

👷‍♂️ Patch fixes
  • Fixes issue where text in <script> and <style> elements should not be decoded or encoded - By @​capricorn86 in task #​1564

v16.2.6

Compare Source

👷‍♂️ Patch fixes
  • Fixes problem where snapshots did not result in HTML for <form> and <select> elements - By @​capricorn86 in task #​1608

v16.2.5

Compare Source

👷‍♂️ Patch fixes
  • Fixes bug where the reference to a parent HTMLFormElement and HTMLSelectElement was wrong which affected the methods remove(), replaceWith(), before(), after(), append(), prepend(), replaceChildren() and insertAdjacentElement() - By @​capricorn86 in task #​1637

v16.2.4

Compare Source

👷‍♂️ Patch fixes
  • Fixes bug where the incorrect location is set after a redirect in BrowserFrame.goto() and DetachedBrowserFrame.goto() - By @​capricorn86 in task #​1627

v16.2.3

Compare Source

👷‍♂️ Patch fixes

v16.2.2

Compare Source

👷‍♂️ Patch fixes
  • Improves error when a Symbol object is being sent to querySelector() or querySelectorAll() as selector - By @​chocolateboy in task #​1640

v16.2.1

Compare Source

👷‍♂️ Patch fixes
  • Set request credentials to "same-origin" in XMLHttpRequest when "withCredentials" is false - By @​saitonakamura in task #​1631

v16.2.0

Compare Source

🎨 Features

v16.1.0

Compare Source

🎨 Features

v16.0.1

Compare Source

👷‍♂️ Patch fixes
  • Fixes problem with children of created documents (e.g. document.implementation.createHTMLDocument()) not being considered as connected to a DOM that was introduced in v16 - By @​capricorn86 in task #​1647

v16.0.0

Compare Source

💣 Breaking Changes
  • Refactors XML and HTML parsing and serialization - By @​capricorn86 in task #​1615
    • This change may break your tests as the serialized output may differ from v15
🎨 Features
👷‍♂️ Patch fixes

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 Jan 6, 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 cli npm v11.0.0 does not support Node.js v18.20.5. This version of npm supports the following node versions: `^20.17.0 || >=22.9.0`. You can find the latest version at https://nodejs.org/.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nuxt/test-utils@3.15.1
npm error Found: happy-dom@16.5.3
npm error node_modules/happy-dom
npm error   dev happy-dom@"16.5.3" from the root project
npm error   peerOptional happy-dom@"*" from vitest@2.1.8
npm error   node_modules/vitest
npm error     dev vitest@"2.1.8" from the root project
npm error     peerOptional vitest@"^0.34.6 || ^1.0.0 || ^2.0.0" from @nuxt/test-utils@3.15.1
npm error     node_modules/@nuxt/test-utils
npm error       dev @nuxt/test-utils@"3.15.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" from @nuxt/test-utils@3.15.1
npm error node_modules/@nuxt/test-utils
npm error   dev @nuxt/test-utils@"3.15.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.15.1
npm error
npm error Conflicting peer dependency: happy-dom@15.11.7
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" from @nuxt/test-utils@3.15.1
npm error   node_modules/@nuxt/test-utils
npm error     dev @nuxt/test-utils@"3.15.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.15.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 /tmp/renovate/cache/others/npm/_logs/2025-01-09T06_37_26_585Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-09T06_37_26_585Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-happy-dom-monorepo branch from 4cff45a to d549e6a Compare January 8, 2025 14:50
@renovate renovate bot force-pushed the renovate/major-happy-dom-monorepo branch from d549e6a to ec2153f Compare January 9, 2025 06:37
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