v2.4.4

Compare Source

What's Changed

• fix: ignore prototype methods when using setData on objects by @​Haberkamp in https://github.com/vuejs/test-utils/pull/2265
• fix: always load cjs bundle in node environment by @​danielroe in https://github.com/vuejs/test-utils/pull/2269
• fix: experimentalVmThreads is now pool=vmThreads by @​cexbrayat in https://github.com/vuejs/test-utils/pull/2275
• feat: respect devtools definition by @​webfansplz in https://github.com/vuejs/test-utils/pull/2311

New Contributors

• @​ArtemTropanets made their first contribution in https://github.com/vuejs/test-utils/pull/2267
• @​Haberkamp made their first contribution in https://github.com/vuejs/test-utils/pull/2265
• @​danielroe made their first contribution in https://github.com/vuejs/test-utils/pull/2269
• @​webfansplz made their first contribution in https://github.com/vuejs/test-utils/pull/2311

Full Changelog: vuejs/test-utils@v2.4.3...v2.4.4

v4.3.0

Compare Source

What's Changed

• Reorganize upload code in prep for merge logic & add more tests by @​robherley in https://github.com/actions/upload-artifact/pull/504
• Add sub-action to merge artifacts by @​robherley in https://github.com/actions/upload-artifact/pull/505

Full Changelog: actions/upload-artifact@v4...v4.3.0

v3.1.5

Compare Source

What's Changed

• action.yml: Update to Node.js 20 by @​hallabro in https://github.com/codecov/codecov-action/pull/1228

New Contributors

• @​hallabro made their first contribution in https://github.com/codecov/codecov-action/pull/1228

Full Changelog: codecov/codecov-action@v3.1.4...v3.1.5

v0.20.0

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.19.0 or ~0.19.0. See npm's documentation about semver for more information.

This time there is only one breaking change, and it only matters for people using Deno. Deno tests that use esbuild will now fail unless you make the change described below.

• Work around API deprecations in Deno 1.40.x (#​3609, #​3611)

  Deno 1.40.0 was just released and introduced run-time warnings about certain APIs that esbuild uses. With this release, esbuild will work around these run-time warnings by using newer APIs if they are present and falling back to the original APIs otherwise. This should avoid the warnings without breaking compatibility with older versions of Deno.

  Unfortunately, doing this introduces a breaking change. The newer child process APIs lack a way to synchronously terminate esbuild's child process, so calling esbuild.stop() from within a Deno test is no longer sufficient to prevent Deno from failing a test that uses esbuild's API (Deno fails tests that create a child process without killing it before the test ends). To work around this, esbuild's stop() function has been changed to return a promise, and you now have to change esbuild.stop() to await esbuild.stop() in all of your Deno tests.

• Reorder implicit file extensions within node_modules (#​3341, #​3608)

  In version 0.18.0, esbuild changed the behavior of implicit file extensions within node_modules directories (i.e. in published packages) to prefer .js over .ts even when the --resolve-extensions= order prefers .ts over .js (which it does by default). However, doing that also accidentally made esbuild prefer .css over .ts, which caused problems for people that published packages containing both TypeScript and CSS in files with the same name.

  With this release, esbuild will reorder TypeScript file extensions immediately after the last JavaScript file extensions in the implicit file extension order instead of putting them at the end of the order. Specifically the default implicit file extension order is .tsx,.ts,.jsx,.js,.css,.json which used to become .jsx,.js,.css,.json,.tsx,.ts in node_modules directories. With this release it will now become .jsx,.js,.tsx,.ts,.css,.json instead.

  Why even rewrite the implicit file extension order at all? One reason is because the .js file is more likely to behave correctly than the .ts file. The behavior of the .ts file may depend on tsconfig.json and the tsconfig.json file may not even be published, or may use extends to refer to a base tsconfig.json file that wasn't published. People can get into this situation when they forget to add all .ts files to their .npmignore file before publishing to npm. Picking .js over .ts helps make it more likely that resulting bundle will behave correctly.

v0.19.12

Compare Source

• The "preserve" JSX mode now preserves JSX text verbatim (#​3605)

  The JSX specification deliberately doesn't specify how JSX text is supposed to be interpreted and there is no canonical way to interpret JSX text. Two most popular interpretations are Babel and TypeScript. Yes they are different (esbuild deliberately follows TypeScript by the way).

  Previously esbuild normalized text to the TypeScript interpretation when the "preserve" JSX mode is active. However, "preserve" should arguably reproduce the original JSX text verbatim so that whatever JSX transform runs after esbuild is free to interpret it however it wants. So with this release, esbuild will now pass JSX text through unmodified:

  // Original code
  let el =
    <a href={'/'} title='&apos;&quot;'> some text
      {foo}
        more text </a>
  
  // Old output (with --loader=jsx --jsx=preserve)
  let el = <a href="/" title={`'"`}>
    {" some text"}
    {foo}
    {"more text "}
  </a>;
  
  // New output (with --loader=jsx --jsx=preserve)
  let el = <a href={"/"} title='&apos;&quot;'> some text
      {foo}
        more text </a>;

• Allow JSX elements as JSX attribute values

  JSX has an obscure feature where you can use JSX elements in attribute position without surrounding them with {...}. It looks like this:

  let el = <div data-ab=<><a/><b/></>/>;

  I think I originally didn't implement it even though it's part of the JSX specification because it previously didn't work in TypeScript (and potentially also in Babel?). However, support for it was silently added in TypeScript 4.8 without me noticing and Babel has also since fixed their bugs regarding this feature. So I'm adding it to esbuild too now that I know it's widely supported.

  Keep in mind that there is some ongoing discussion about removing this feature from JSX. I agree that the syntax seems out of place (it does away with the elegance of "JSX is basically just XML with {...} escapes" for something arguably harder to read, which doesn't seem like a good trade-off), but it's in the specification and TypeScript and Babel both implement it so I'm going to have esbuild implement it too. However, I reserve the right to remove it from esbuild if it's ever removed from the specification in the future. So use it with caution.

• Fix a bug with TypeScript type parsing (#​3574)

  This release fixes a bug with esbuild's TypeScript parser where a conditional type containing a union type that ends with an infer type that ends with a constraint could fail to parse. This was caused by the "don't parse a conditional type" flag not getting passed through the union type parser. Here's an example of valid TypeScript code that previously failed to parse correctly:

  type InferUnion<T> = T extends { a: infer U extends number } | infer U extends number ? U : never

v4.0.3

Compare Source

Bug Fixes

• handle empty build (#​357) (3bddb9d)
• types: support NodeNext (037bb99), closes #​342

Reverts

• .env file (d35279c)

v48.0.4

Compare Source

Bug Fixes

• require-description-complete-sentence: capture multiple newlines as "paragraphs"; fixes #​1193 (c5f203a)

v48.0.3

Compare Source

Bug Fixes

• require-jsdoc: ensure children of TS type reference and parameter instantiation can be exports; fixes #​1186 (7461e01)
• require-param: skip this parameter in checks (when followed by destructured content); fixes #​1190 (0cd761b)
• update devDeps. (6b163c8)

v3.23.2

Compare Source

v1.10.1

Compare Source

compare changes

🩹 Fixes

• setResponseHeaders: Fix types to allow partial header names (#​607)
• setCookie: Allow cookies with the same name but different options (#​606)
• getRequestWebStream: Reuse buffered body if available (#​616)
• getSession: Use semaphore lock for unseal operation (#​612)
• getRequestIP: Use first address of x-forwarded-for header (#​618)
• Avoid setting default content-type for responses with 304 status (#​641)

💅 Refactors

• Use H3Event.node.res for internal types (#​626)

📖 Documentation

• Fix getRequestHeaders signuture (#​613)
• Fix typo in examples (#​631)

🏡 Chore

• release: V1.10.0 (ae91fc8)
• Update lockfile (1f9393d)
• Rename vitest config file to supress warn (8345c1f)
• Update lockfile (87119a1)

✅ Tests

• Add basic tests for session (22807f2)
• Update session test (ba275c3)

❤️ Contributors

• Pooya Parsa (@​pi0)
• Estéban (@​Barbapapazes)
• Michael Brevard <yonshi29@​gmail.com>
• Jaden me@jaden.bio
• Oscar Beaumont (@​oscartbeaumont)
• Kamil Kuczmera
• Jonas Thelemann e-mail@jonas-thelemann.de

v13.3.4

Compare Source

👷‍♂️ Patch fixes

• Fixes automatic release notes in the Github Workflow - By @​capricorn86 in task #​1241

v13.3.3

Compare Source

👷‍♂️ Patch fixes

• Updates documentation. (#​1240)

v13.3.2

Compare Source

v13.3.1

Compare Source

👷‍♂️ Patch fixes

• Improves documentation for "@​happy-dom/global-registrator". (#​1233)

v13.3.0

Compare Source

🎨 Features

• Adds support for sending in Window options to GlobalRegistrator.register() in "@​happy-dom/global-registrator". (#​1105)

👷‍♂️ Patch fixes

• Fixes problem with getters and setters not being added to the global object when using GlobalRegistrator.register() in "@​happy-dom/global-registrator". (#​1105)

v13.2.2

Compare Source

👷‍♂️ Patch fixes

• Fixes issue where it is not possible to set global.location.href when using Happy DOM in the global scope (e.g. by using @​happy-dom/global-registrator). (#​1230)

v13.2.1

Compare Source

👷‍♂️ Patch fixes

• Adds missing element classes and types to the export in "index.js", so that they are easier to import. The missing elements was HTMLAnchorElement, HTMLButtonElement, HTMLOptGroupElement, HTMLOptionElement, HTMLUnknownElement and HTMLSelectElement. (#​1227)
• Adds non-implemented element classes to the export in "index.js" by exporting HTMLElement as the non-implemented class name. (#​1227)

v0.39.0: 0.39.0

Compare Source

• Update markdownlint dependency to 0.33.0
  • Add MD055/table-pipe-style, MD056/table-column-count
  • Improve MD005/MD007/MD024/MD026/MD038
  • Incorporate micromark-extension-directive
  • Improve JSON schema, document validation
• Handle trailing commas in JSONC configuration
• Update all dependencies via Dependabot

v0.3.6

Compare Source

compare changes

🚀 Enhancements

• Allow installing multiple dependencies (#​107)

📦 Build

• cli: Only import required fields from package.json to the bundle (591dd4d)

🏡 Chore

• Update lockfile (84d90d7)

🤖 CI

• Increase timeout for windows (da4a986)

❤️ Contributors

• Pooya Parsa (@​pi0)

v0.3.5

Compare Source

v1.41.1

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/29067 - [REGRESSION] Codegen/Recorder: not all clicks are being actioned nor recordedhttps://github.com/microsoft/playwright/issues/290288 - [REGRESSION] React component tests throw type error when passing null/undefined to componenhttps://github.com/microsoft/playwright/issues/2902727 - [REGRESSION] React component tests not passing Date prop valuhttps://github.com/microsoft/playwright/issues/29023023 - [REGRESSION] React component tests not rendering children phttps://github.com/microsoft/playwright/issues/290199019 - [REGRESSION] trace.playwright.dev does not currently support the loading from URL

Browser Versions

• Chromium 121.0.6167.57
• Mozilla Firefox 121.0
• WebKit 17.4

This version was also tested against the following stable channels:

• Google Chrome 120
• Microsoft Edge 120

v8.15.0

Compare Source

Minor Changes

• When the license field does not exist in package.json but a license file exists, try to match and extract the license name #​7530.

Patch Changes

• Running pnpm update -r --latest will no longer downgrade prerelease dependencies #​7436.
• --aggregate-output should work on scripts executed from the same project #​7556.
• Prefer hard links over reflinks on Windows as they perform better #​7564.
• Reduce the length of the side-effects cache key. Instead of saving a stringified object composed from the dependency versions of the package, use the hash calculated from the said object #​7563.
• Throw an error if pnpm update --latest runs with arguments containing versions specs. For instance, pnpm update --latest foo@next is not allowed #​7567.
• Don't fail in Windows CoW if the file already exists #​7554.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.14.3

Compare Source

Patch Changes

• pnpm pack should work as expected when "prepack" modifies the manifest #​7558.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.14.2

Compare Source

Patch Changes

• Registry configuration from previous installation should not override current settings #​7507.
• pnpm dlx should not fail, when executed from package.json "scripts" 7424.
• A git-hosted dependency should not be added to the store if it failed to be built #​7407.
• pnpm publish should pack "main" file or "bin" files defined in "publishConfig" #​4195.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

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. 👻 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.