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 #104

Merged
merged 1 commit into from
Dec 17, 2023
Merged

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

merged 1 commit into from
Dec 17, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 11, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) ^20.10.3 -> ^20.10.4 age adoption passing confidence
@vitest/coverage-v8 (source) ^1.0.1 -> ^1.0.4 age adoption passing confidence
esbuild ^0.19.8 -> ^0.19.9 age adoption passing confidence
eslint (source) ^8.55.0 -> ^8.56.0 age adoption passing confidence
pnpm (source) 8.11.0 -> 8.12.1 age adoption passing confidence
prettier (source) ^3.1.0 -> ^3.1.1 age adoption passing confidence
rollup (source) ^4.6.1 -> ^4.9.0 age adoption passing confidence
typescript (source) ^5.3.2 -> ^5.3.3 age adoption passing confidence
vitest (source) ^1.0.1 -> ^1.0.4 age adoption passing confidence

Release Notes

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

v1.0.4

Compare Source

The previous release was built incorrectly and didn't include the performance fix. This release fixes that.

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v1.0.3

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v1.0.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
evanw/esbuild (esbuild)

v0.19.9

Compare Source

  • Add support for transforming new CSS gradient syntax for older browsers

    The specification called CSS Images Module Level 4 introduces new CSS gradient syntax for customizing how the browser interpolates colors in between color stops. You can now control the color space that the interpolation happens in as well as (for "polar" color spaces) control whether hue angle interpolation happens clockwise or counterclockwise. You can read more about this in Mozilla's blog post about new CSS gradient features.

    With this release, esbuild will now automatically transform this syntax for older browsers in the target list. For example, here's a gradient that should appear as a rainbow in a browser that supports this new syntax:

    /* Original code */
.rainbow-gradient {
  width: 100px;
  height: 100px;
  background: linear-gradient(in hsl longer hue, #​7ff, #​77f);
}

/* New output (with --target=chrome99) */
.rainbow-gradient {
  width: 100px;
  height: 100px;
  background:
    linear-gradient(
      #​77ffff,
      #​77ffaa 12.5%,
      #​77ff80 18.75%,
      #​84ff77 21.88%,
      #​99ff77 25%,
      #eeff77 37.5%,
      #fffb77 40.62%,
      #ffe577 43.75%,
      #ffbb77 50%,
      #ff9077 56.25%,
      #ff7b77 59.38%,
      #ff7788 62.5%,
      #ff77dd 75%,
      #ff77f2 78.12%,
      #f777ff 81.25%,
      #cc77ff 87.5%,
      #​7777ff);
}

    You can now use this syntax in your CSS source code and esbuild will automatically convert it to an equivalent gradient for older browsers. In addition, esbuild will now also transform "double position" and "transition hint" syntax for older browsers as appropriate:

    /* Original code */
.stripes {
  width: 100px;
  height: 100px;
  background: linear-gradient(#e65 33%, #ff2 33% 67%, #​99e 67%);
}
.glow {
  width: 100px;
  height: 100px;
  background: radial-gradient(white 10%, 20%, black);
}

/* New output (with --target=chrome33) */
.stripes {
  width: 100px;
  height: 100px;
  background:
    linear-gradient(
      #e65 33%,
      #ff2 33%,
      #ff2 67%,
      #​99e 67%);
}
.glow {
  width: 100px;
  height: 100px;
  background:
    radial-gradient(
      #ffffff 10%,
      #aaaaaa 12.81%,
      #​959595 15.62%,
      #​7b7b7b 21.25%,
      #​5a5a5a 32.5%,
      #​444444 43.75%,
      #​323232 55%,
      #​161616 77.5%,
      #​000000);
}

    You can see visual examples of these new syntax features by looking at esbuild's gradient transformation tests.

    If necessary, esbuild will construct a new gradient that approximates the original gradient by recursively splitting the interval in between color stops until the approximation error is within a small threshold. That is why the above output CSS contains many more color stops than the input CSS.

    Note that esbuild deliberately replaces the original gradient with the approximation instead of inserting the approximation before the original gradient as a fallback. The latest version of Firefox has multiple gradient rendering bugs (including incorrect interpolation of partially-transparent colors and interpolating non-sRGB colors using the incorrect color space). If esbuild didn't replace the original gradient, then Firefox would use the original gradient instead of the fallback the appearance would be incorrect in Firefox. In other words, the latest version of Firefox supports modern gradient syntax but interprets it incorrectly.

  • Add support for color(), lab(), lch(), oklab(), oklch(), and hwb() in CSS

    CSS has recently added lots of new ways of specifying colors. You can read more about this in Chrome's blog post about CSS color spaces.

    This release adds support for minifying colors that use the color(), lab(), lch(), oklab(), oklch(), or hwb() syntax and/or transforming these colors for browsers that don't support it yet:

    /* Original code */
div {
  color: hwb(90deg 20% 40%);
  background: color(display-p3 1 0 0);
}

/* New output (with --target=chrome99) */
div {
  color: #​669933;
  background: #ff0f0e;
  background: color(display-p3 1 0 0);
}

    As you can see, colors outside of the sRGB color space such as color(display-p3 1 0 0) are mapped back into the sRGB gamut and inserted as a fallback for browsers that don't support the new color syntax.

  • Allow empty type parameter lists in certain cases (#​3512)

    TypeScript allows interface declarations and type aliases to have empty type parameter lists. Previously esbuild didn't handle this edge case but with this release, esbuild will now parse this syntax:

    interface Foo<> {}
type Bar<> = {}

    This fix was contributed by @​magic-akari.

eslint/eslint (eslint)

v8.56.0

Compare Source

Features
  • 0dd9704 feat: Support custom severity when reporting unused disable directives (#​17212) (Bryan Mishkin)
  • 31a7e3f feat: fix no-restricted-properties false negatives with unknown objects (#​17818) (Arka Pratim Chaudhuri)
Bug Fixes
  • 7d5e5f6 fix: TypeError: fs.exists is not a function on read-only file system (#​17846) (Francesco Trotta)
  • 74739c8 fix: suggestion with invalid syntax in no-promise-executor-return rule (#​17812) (Bryan Mishkin)
Documentation
  • 9007719 docs: update link in ways-to-extend.md (#​17839) (Amel SELMANE)
  • 3a22236 docs: Update README (GitHub Actions Bot)
  • 54c3ca6 docs: fix migration-guide example (#​17829) (Tanuj Kanti)
  • 4391b71 docs: check config comments in rule examples (#​17815) (Francesco Trotta)
  • fd28363 docs: remove mention about ESLint stylistic rules in readme (#​17810) (Zwyx)
  • 48ed5a6 docs: Update README (GitHub Actions Bot)
Chores
pnpm/pnpm (pnpm)

v8.12.1

Compare Source

Patch Changes

  • Don't report dependencies with optional dependencies as being added on repeat install. This was a bug in reporting #​7384.
  • Fix a bug where --fix-lockfile crashes on tarballs #​7368.
  • Do not create empty patch directory.
  • Installation should not fail if an empty node_modules directory cannot be removed #​7405.

Our Gold Sponsors

Our Silver Sponsors

v8.12.0

Compare Source

Minor Changes

  • Add support for basic authorization header #​7371.

Patch Changes

  • Fix a bug where pnpm incorrectly passes a flag to a run handler as a fallback command #​7244.
  • When dedupe-direct-deps is set to true, commands of dependencies should be deduplicated #​7359.

Our Gold Sponsors

Our Silver Sponsors
prettier/prettier (prettier)

v3.1.1

Compare Source

diff

Fix config file search (#​15363 by @​fisker)

Previously, we start search for config files from the filePath as a directory, if it happened to be a directory and contains config file, it will be used by mistake.

├─ .prettierrc
└─ test.js         (A directory)
  └─ .prettierrc

// Prettier 3.1.0
await prettier.resolveConfigFile(new URL("./test.js", import.meta.url));
// <CWD>/test.js/.prettierrc

// Prettier 3.1.1
await prettier.resolveConfigFile(new URL("./test.js", import.meta.url));
// <CWD>/.prettierrc
Skip explicitly passed symbolic links with --no-error-on-unmatched-pattern (#​15533 by @​sanmai-NL)

Since Prettier v3, we stopped following symbolic links, however in some use cases, the symbolic link patterns can't be filtered out, and there is no way to prevent Prettier from throwing errors.

In Prettier 3.1.1, you can use --no-error-on-unmatched-pattern to simply skip symbolic links.

Consistently use tabs in ternaries when useTabs is true (#​15662 by @​auvred)
// Input
aaaaaaaaaaaaaaa
	? bbbbbbbbbbbbbbbbbb
	: ccccccccccccccc
	  ? ddddddddddddddd
	  : eeeeeeeeeeeeeee
	    ? fffffffffffffff
	    : gggggggggggggggg;

// Prettier 3.1.0
aaaaaaaaaaaaaaa
	? bbbbbbbbbbbbbbbbbb
	: ccccccccccccccc
	  ? ddddddddddddddd
	  : eeeeeeeeeeeeeee
	    ? fffffffffffffff
	    : gggggggggggggggg;

// Prettier 3.1.1
aaaaaaaaaaaaaaa
	? bbbbbbbbbbbbbbbbbb
	: ccccccccccccccc
		? ddddddddddddddd
		: eeeeeeeeeeeeeee
			? fffffffffffffff
			: gggggggggggggggg;
Improve config file search (#​15663 by @​fisker)

The Prettier config file search performance has been improved by more effective cache strategy.

Fix unstable and ugly formatting for comments in destructuring patterns (#​15708 by @​sosukesuzuki)
// Input
const {
  foo,
  // bar
  // baz
}: Foo = expr;

// Prettier 3.1.0
const {
  foo1,
} // bar
// baz
: Foo = expr;

// Prettier 3.1.0 second output
const {
  foo1, // bar
} // baz
: Foo = expr;

// Prettier 3.1.1
const {
  foo1,
  // bar
  // baz
}: Foo = expr;
Support "Import Attributes" (#​15718 by @​fisker)

TypeScript 5.3 supports the latest updates to the import attributes proposal.

import something from "./something.json" with { type: "json" };
Fix false claim in docs that cursorOffset is incompatible with rangeStart/rangeEnd (#​15750 by @​ExplodingCabbage)

The cursorOffset option has in fact been compatible with rangeStart/rangeEnd for over 5 years, thanks to work by @​ds300. However, Prettier's documentation (including the CLI --help text) continued to claim otherwise, falsely. The documentation is now fixed.

Keep curly braces and from keyword in empty import statements (#​15756 by @​fisker)
// Input
import { } from 'foo';
import { /* comment */ } from 'bar';

// Prettier 3.1.0
import {} from "foo";
import /* comment */ "bar";

// Prettier 3.1.1
import {} from "foo";
import {} from /* comment */ "bar";
Keep empty import attributes and assertions (#​15757 by @​fisker)
// Input
import foo from "foo" with {};
import bar from "bar" assert {};

// Prettier 3.1.0
import foo from "foo";
import bar from "bar";

// Prettier 3.1.1
import foo from "foo" with {};
import bar from "bar" assert {};
rollup/rollup (rollup)

v4.9.0

Compare Source

2023-12-13

Features
  • Fully support arbitrary strings as import and export identifiers (#​5298)
Pull Requests

v4.8.0

Compare Source

2023-12-11

Features
  • Improve experimentalMinChunkSize to take already loaded modules from dynamic imports into account (#​5294)
Pull Requests

v4.7.0

Compare Source

2023-12-08

Features
  • Add build for Linux riscv64 architecture (#​5288)
Bug Fixes
  • Improve error message when native Windows build does not start (#​5284)
Pull Requests
Microsoft/TypeScript (typescript)

v5.3.3: TypeScript 5.3.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

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.

@codecov Codecov
Copy link

codecov bot commented Dec 11, 2023 •
edited
Loading

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (bfaedd7) 80.46% compared to head (0b54398) 80.46%.

Additional details and impacted files 
@@           Coverage Diff           @@
##             main     #104   +/-   ##
=======================================
  Coverage   80.46%   80.46%           
=======================================
  Files          10       10           
  Lines         343      343           
  Branches       32       32           
=======================================
  Hits          276      276           
  Misses         61       61           
  Partials        6        6

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from f36f963 to 3513416 Compare December 13, 2023 10:55
@renovate renovate bot merged commit 4c097fe into main Dec 17, 2023
4 checks passed
@renovate renovate bot deleted the renovate/all-minor-patch branch December 17, 2023 01:08
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.
0 participants