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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update all non-major dependencies #72

Closed
wants to merge 1 commit into from
Closed

chore(deps): update all non-major dependencies #72

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 9, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/coverage-c8 (source) ^0.31.0 -> ^0.33.0 age adoption passing confidence
changelogen ^0.5.3 -> ^0.5.5 age adoption passing confidence
esbuild ^0.17.18 -> ^0.20.2 age adoption passing confidence
eslint (source) ^8.39.0 -> ^8.57.0 age adoption passing confidence
eslint-config-unjs ^0.1.0 -> ^0.2.1 age adoption passing confidence
pnpm (source) 8.13.1 -> 8.15.5 age adoption passing confidence
typescript (source) ^5.0.4 -> ^5.4.3 age adoption passing confidence
vitest (source) ^0.31.0 -> ^0.34.6 age adoption passing confidence

Release Notes

vitest-dev/vitest (@​vitest/coverage-c8)

v0.33.0

Compare Source

   🚨 Breaking Changes
  • Revert default include patterns  -  by @​so1ve #​3729
    • 0.32.0 changed the default include globs to be compatible with Jest. After a discussion with the community, we are reverting this change because it turned out to be non-intuitive.
   🐞 Bug Fixes
    View changes on GitHub

v0.32.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.32.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.32.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.32.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.32.0

Compare Source

   🚨 Breaking Changes
  • Throw an error, if the module cannot be resolved  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3307 (1ad63)
    • Vitest used to fall back to the original import when it could not resolve it to the file path or the virtual module. This leads to hard-to-find module graph mismatches if you had incorrect alias or relied on relative imports to be resolved to the project root (which is usual behavior in TypeScript) because the code accidentally "worked". With this release, Vitest will now throw an error if it cannot resolve the module - there are possible edge cases that are not covered yet, so if you have any problems with this, please open a separate issue with reproduction.
  • Improve globs  -  by @​nickmccurdy in https://github.com/vitest-dev/vitest/issues/3392 (19ecc)
    • Vitest now has glob patterns similar to Jest for better compatibility. It's possible that some files will be considered test files when previously they were not. For example, Vitest now considers test.js to be a test file. Also any file in __tests__ is now considered to be a test, not just files with test or spec suffix.
  • Add @vitest/coverage-v8 package  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/3339 (82112)
    • Vitest now uses v8 code coverage directly for better performance. @vitest/coverage-c8 is deprecated as Vitest no longer uses c8 package for coverage output. It will not be updated anymore, and Vitest will fail in the next version if the user has c8 as their coverage provider. Please, install the new @vitest/coverage-v8 package if you previously used @vitest/coverage-c8.
  • mocker: Don't restore mock to the original if the module is automocked  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3518 (c1004)
    • spy.mockRestore on auto-mocked named exports will no longer restore their implementation to the actual function. This behavior better matches what Jest does.
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
unjs/changelogen (changelogen)

v0.5.5

Compare Source

compare changes

🚀 Enhancements
🩹 Fixes
  • Extra spaces in contributors and breaking changes (#​134)
  • Repo name with - or . (#​127)
🏡 Chore
❤️ Contributors

v0.5.4

Compare Source

compare changes

🚀 Enhancements
  • Support --publish and --canary (#​123)
🩹 Fixes
  • markdown: Remove unnecessary spaces (#​106)
  • Add missing type export to package.json (#​113)
📖 Documentation
  • Add documentation about --push flag (#​114)
❤️ Contributors
evanw/esbuild (esbuild)

v0.20.2

Compare Source

  • Support TypeScript experimental decorators on abstract class fields (#​3684)

    With this release, you can now use TypeScript experimental decorators on abstract class fields. This was silently compiled incorrectly in esbuild 0.19.7 and below, and was an error from esbuild 0.19.8 to esbuild 0.20.1. Code such as the following should now work correctly:

    // Original code
const log = (x: any, y: string) => console.log(y)
abstract class Foo { @​log abstract foo: string }
new class extends Foo { foo = '' }

// Old output (with --loader=ts --tsconfig-raw={\"compilerOptions\":{\"experimentalDecorators\":true}})
const log = (x, y) => console.log(y);
class Foo {
}
new class extends Foo {
  foo = "";
}();

// New output (with --loader=ts --tsconfig-raw={\"compilerOptions\":{\"experimentalDecorators\":true}})
const log = (x, y) => console.log(y);
class Foo {
}
__decorateClass([
  log
], Foo.prototype, "foo", 2);
new class extends Foo {
  foo = "";
}();

  • JSON loader now preserves __proto__ properties (#​3700)

    Copying JSON source code into a JavaScript file will change its meaning if a JSON object contains the __proto__ key. A literal __proto__ property in a JavaScript object literal sets the prototype of the object instead of adding a property named __proto__, while a literal __proto__ property in a JSON object literal just adds a property named __proto__. With this release, esbuild will now work around this problem by converting JSON to JavaScript with a computed property key in this case:

    // Original code
import data from 'data:application/json,{"__proto__":{"fail":true}}'
if (Object.getPrototypeOf(data)?.fail) throw 'fail'

// Old output (with --bundle)
(() => {
  // <data:application/json,{"__proto__":{"fail":true}}>
  var json_proto_fail_true_default = { __proto__: { fail: true } };

  // entry.js
  if (Object.getPrototypeOf(json_proto_fail_true_default)?.fail)
    throw "fail";
})();

// New output (with --bundle)
(() => {
  // <data:application/json,{"__proto__":{"fail":true}}>
  var json_proto_fail_true_default = { ["__proto__"]: { fail: true } };

  // example.mjs
  if (Object.getPrototypeOf(json_proto_fail_true_default)?.fail)
    throw "fail";
})();

  • Improve dead code removal of switch statements (#​3659)

    With this release, esbuild will now remove switch statements in branches when minifying if they are known to never be evaluated:

    // Original code
if (true) foo(); else switch (bar) { case 1: baz(); break }

// Old output (with --minify)
if(1)foo();else switch(bar){case 1:}

// New output (with --minify)
foo();

  • Empty enums should behave like an object literal (#​3657)

    TypeScript allows you to create an empty enum and add properties to it at run time. While people usually use an empty object literal for this instead of a TypeScript enum, esbuild's enum transform didn't anticipate this use case and generated undefined instead of {} for an empty enum. With this release, you can now use an empty enum to generate an empty object literal.

    // Original code
enum Foo {}

// Old output (with --loader=ts)
var Foo = /* @&#8203;__PURE__ */ ((Foo2) => {
})(Foo || {});

// New output (with --loader=ts)
var Foo = /* @&#8203;__PURE__ */ ((Foo2) => {
  return Foo2;
})(Foo || {});

  • Handle Yarn Plug'n'Play edge case with tsconfig.json (#​3698)

    Previously a tsconfig.json file that extends another file in a package with an exports map failed to work when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

  • Work around issues with Deno 1.31+ (#​3682)

    Version 0.20.0 of esbuild changed how the esbuild child process is run in esbuild's API for Deno. Previously it used Deno.run but that API is being removed in favor of Deno.Command. As part of this change, esbuild is now calling the new unref function on esbuild's long-lived child process, which is supposed to allow Deno to exit when your code has finished running even though the child process is still around (previously you had to explicitly call esbuild's stop() function to terminate the child process for Deno to be able to exit).

    However, this introduced a problem for Deno's testing API which now fails some tests that use esbuild with error: Promise resolution is still pending but the event loop has already resolved. It's unclear to me why this is happening. The call to unref was recommended by someone on the Deno core team, and calling Node's equivalent unref API has been working fine for esbuild in Node for a long time. It could be that I'm using it incorrectly, or that there's some reference counting and/or garbage collection bug in Deno's internals, or that Deno's unref just works differently than Node's unref. In any case, it's not good for Deno tests that use esbuild to be failing.

    In this release, I am removing the call to unref to fix this issue. This means that you will now have to call esbuild's stop() function to allow Deno to exit, just like you did before esbuild version 0.20.0 when this regression was introduced.

    Note: This regression wasn't caught earlier because Deno doesn't seem to fail tests that have outstanding setTimeout calls, which esbuild's test harness was using to enforce a maximum test runtime. Adding a setTimeout was allowing esbuild's Deno tests to succeed. So this regression doesn't necessarily apply to all people using tests in Deno.

v0.20.1

Compare Source

  • Fix a bug with the CSS nesting transform (#​3648)

    This release fixes a bug with the CSS nesting transform for older browsers where the generated CSS could be incorrect if a selector list contained a pseudo element followed by another selector. The bug was caused by incorrectly mutating the parent rule's selector list when filtering out pseudo elements for the child rules:

    /* Original code */
.foo {
  &:after,
  & .bar {
    color: red;
  }
}

/* Old output (with --supported:nesting=false) */
.foo .bar,
.foo .bar {
  color: red;
}

/* New output (with --supported:nesting=false) */
.foo:after,
.foo .bar {
  color: red;
}

  • Constant folding for JavaScript inequality operators (#​3645)

    This release introduces constant folding for the < > <= >= operators. The minifier will now replace these operators with true or false when both sides are compile-time numeric or string constants:

    // Original code
console.log(1 < 2, '🍕' > '🧀')

// Old output (with --minify)
console.log(1<2,"🍕">"🧀");

// New output (with --minify)
console.log(!0,!1);

  • Better handling of __proto__ edge cases (#​3651)

    JavaScript object literal syntax contains a special case where a non-computed property with a key of __proto__ sets the prototype of the object. This does not apply to computed properties or to properties that use the shorthand property syntax introduced in ES6. Previously esbuild didn't correctly preserve the "sets the prototype" status of properties inside an object literal, meaning a property that sets the prototype could accidentally be transformed into one that doesn't and vice versa. This has now been fixed:

    // Original code
function foo(__proto__) {
  return { __proto__: __proto__ } // Note: sets the prototype
}
function bar(__proto__, proto) {
  {
    let __proto__ = proto
    return { __proto__ } // Note: doesn't set the prototype
  }
}

// Old output
function foo(__proto__) {
  return { __proto__ }; // Note: no longer sets the prototype (WRONG)
}
function bar(__proto__, proto) {
  {
    let __proto__2 = proto;
    return { __proto__: __proto__2 }; // Note: now sets the prototype (WRONG)
  }
}

// New output
function foo(__proto__) {
  return { __proto__: __proto__ }; // Note: sets the prototype (correct)
}
function bar(__proto__, proto) {
  {
    let __proto__2 = proto;
    return { ["__proto__"]: __proto__2 }; // Note: doesn't set the prototype (correct)
  }
}

  • Fix cross-platform non-determinism with CSS color space transformations (#​3650)

    The Go compiler takes advantage of "fused multiply and add" (FMA) instructions on certain processors which do the operation x*y + z without intermediate rounding. This causes esbuild's CSS color space math to differ on different processors (currently ppc64le and s390x), which breaks esbuild's guarantee of deterministic output. To avoid this, esbuild's color space math now inserts a float64() cast around every single math operation. This tells the Go compiler not to use the FMA optimization.

  • Fix a crash when resolving a path from a directory that doesn't exist (#​3634)

    This release fixes a regression where esbuild could crash when resolving an absolute path if the source directory for the path resolution operation doesn't exist. While this situation doesn't normally come up, it could come up when running esbuild concurrently with another operation that mutates the file system as esbuild is doing a build (such as using git to switch branches). The underlying problem was a regression that was introduced in version 0.18.0.

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

Configuration

📅 Schedule: Branch creation - "after 2am and before 3am" (UTC), Automerge - "after 1am and before 2am" (UTC).

🚦 Automerge: Enabled.

♻ 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 force-pushed the renovate/all-minor-patch branch 2 times, most recently from d65dd8d to 4701f43 Compare May 13, 2023 02:52
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from b2be5d4 to 34cda69 Compare May 24, 2023 14:14
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 8456bde to e52b589 Compare June 6, 2023 19:02
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from aefa9e2 to c4b7b8c Compare June 16, 2023 17:00
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from ba10c0c to 00b7413 Compare June 23, 2023 13:48
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from 92862aa to ccdc185 Compare July 1, 2023 02:37
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 29d97da to 8adbc2e Compare July 3, 2023 10:53
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from da6ad5b to 97dce1b Compare December 10, 2023 07:36
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from f3d907d to 262908d Compare December 19, 2023 03:18
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 052ad75 to cbbf8f0 Compare December 29, 2023 21:47
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from cbbf8f0 to 2066ad7 Compare January 3, 2024 00:35
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 2066ad7 to 7b89445 Compare January 10, 2024 15:29
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from bc028ea to 5141356 Compare January 27, 2024 21:08
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5141356 to b8aeb6c Compare January 29, 2024 23:22
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 3a6070d to c6f303b Compare February 19, 2024 11:11
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from db8df83 to 957beff Compare February 24, 2024 16:11
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from e929d20 to ae0ee2a Compare March 8, 2024 07:09
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from de572ec to 12cee39 Compare March 20, 2024 20:02
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from d4a899e to 6364702 Compare March 29, 2024 18:37
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 6364702 to 6698a40 Compare March 29, 2024 18:38
@pi0 pi0 closed this Mar 29, 2024
@renovate renovate bot deleted the renovate/all-minor-patch branch March 29, 2024 18:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@pi0