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

fix(deps): update dependencies (non-major) #1072

Merged
merged 1 commit into from
Dec 22, 2023
Merged

fix(deps): update dependencies (non-major) #1072

merged 1 commit into from
Dec 22, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 22, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@babel/core (source) ^7.23.5 -> ^7.23.6 age adoption passing confidence
@easyops-cn/docusaurus-search-local ^0.38.1 -> ^0.40.0 age adoption passing confidence
@rushstack/eslint-patch (source) ^1.6.0 -> ^1.6.1 age adoption passing confidence
@types/react (source) ^18.2.42 -> ^18.2.45 age adoption passing confidence
@types/react-dom (source) ^18.2.17 -> ^18.2.18 age adoption passing confidence
@typescript-eslint/eslint-plugin (source) ^6.13.2 -> ^6.15.0 age adoption passing confidence
@typescript-eslint/parser (source) ^6.13.2 -> ^6.15.0 age adoption passing confidence
eslint (source) ^8.55.0 -> ^8.56.0 age adoption passing confidence
eslint-plugin-import ^2.29.0 -> ^2.29.1 age adoption passing confidence
eslint-plugin-jsonc (source) ^2.10.0 -> ^2.11.2 age adoption passing confidence
eslint-plugin-n ^16.3.1 -> ^16.5.0 age adoption passing confidence
eslint-plugin-prettier ^5.0.1 -> ^5.1.1 age adoption passing confidence
eslint-plugin-yml (source) ^1.10.0 -> ^1.11.0 age adoption passing confidence
html-webpack-plugin ^5.5.4 -> ^5.6.0 age adoption passing confidence
prettier (source) ^3.1.0 -> ^3.1.1 age adoption passing confidence
react-router-dom (source) ^6.20.1 -> ^6.21.1 age adoption passing confidence
tailwindcss (source) ^3.3.6 -> ^3.4.0 age adoption passing confidence

Release Notes

babel/babel (@​babel/core)

v7.23.6

Compare Source

👓 Spec Compliance
  • babel-generator, babel-parser, babel-types
  • babel-helpers, babel-plugin-proposal-decorators, babel-plugin-transform-class-properties, babel-plugin-transform-class-static-block, babel-plugin-transform-runtime, babel-preset-env, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime, babel-types
🐛 Bug Fix
  • babel-generator
  • babel-helpers, babel-plugin-proposal-explicit-resource-management
  • babel-plugin-proposal-decorators, babel-plugin-transform-class-properties
    • #​16161 Ensure the [[@​@​toPrimitive]] call of a decorated class member key is invoked once (@​JLHwung)
    • #​16148 Support named evaluation for decorated anonymous class exp (@​JLHwung)
  • babel-plugin-transform-for-of, babel-preset-env
  • babel-helpers, babel-plugin-proposal-decorators, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime
  • babel-plugin-transform-typescript
🔬 Output optimization
  • babel-helper-create-class-features-plugin, babel-plugin-transform-class-properties
  • babel-helpers, babel-plugin-proposal-decorators
easyops-cn/docusaurus-search-local (@​easyops-cn/docusaurus-search-local)

v0.40.0

Compare Source

Features
  • allow force enable search index even if noIndex: true is set (09d0f30), closes #​385
  • support i18n for search context labels (83b05a2)

v0.39.0

Compare Source

Features
microsoft/rushstack (@​rushstack/eslint-patch)

v1.6.1

Compare Source

Fri, 15 Dec 2023 01:10:06 GMT

Patches
  • Fix bulk suppression patch's eslintrc detection in polyrepos
typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v6.15.0

Compare Source

Features

You can read about our versioning strategy and releases on our website.

v6.14.0

Compare Source

Bug Fixes
  • eslint-plugin: add no-unsafe-unary-minus, prefer-destructuring to disable-type-checked (#​8038) (431cd15)
  • eslint-plugin: correct message for no-unsafe-unary-minus (#​7998) (705370a)
Features
  • eslint-plugin: [explicit-function-return-type] add support for typed class property definitions (#​8027) (bff47d7)
  • eslint-plugin: [require-await] allow yielding Promise in async generators (#​8003) (4c3e704)

You can read about our versioning strategy and releases on our website.

6.13.2 (2023-12-04)

Note: Version bump only for package @​typescript-eslint/eslint-plugin

You can read about our versioning strategy and releases on our website.

6.13.1 (2023-11-28)

Note: Version bump only for package @​typescript-eslint/eslint-plugin

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v6.15.0

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

You can read about our versioning strategy and releases on our website.

v6.14.0

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

You can read about our versioning strategy and releases on our website.

6.13.2 (2023-12-04)

Note: Version bump only for package @​typescript-eslint/parser

You can read about our versioning strategy and releases on our website.

6.13.1 (2023-11-28)

Note: Version bump only for package @​typescript-eslint/parser

You can read about our versioning strategy and releases on our website.

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
import-js/eslint-plugin-import (eslint-plugin-import)

v2.29.1

Compare Source

Fixed
ota-meshi/eslint-plugin-jsonc (eslint-plugin-jsonc)

v2.11.2

Compare Source

Patch Changes

v2.11.1

Compare Source

Patch Changes

v2.11.0

Compare Source

Minor Changes
eslint-community/eslint-plugin-n (eslint-plugin-n)

v16.5.0

Compare Source

Features

  • feat: Add builtins check for ES2021 to no-unsupported-features/es-builtins rule (#​153) (15a5850)
  • feat: Add syntax check for ES2021 to no-unsupported-features/es-syntax rule (#​152) (6835a10)

Docs & Chores

  • docs: Auto-generate configs list with eslint-doc-generator (#​146) (6409e34)
  • chore: Configure Renovate (0d6a0fe)

v16.4.0

Compare Source

prettier/eslint-plugin-prettier (eslint-plugin-prettier)

v5.1.1

Compare Source

Patch Changes

v5.1.0

Compare Source

Minor Changes

  • #​616 3856413 Thanks @​BPScott! - Add recommended config for the flat config format.

    If you are using flat config, import the recommended config from eslint-plugin-prettier/recommended. Like the legacy format recommended config, this automatically includes the contents of eslint-config-prettier.

    // eslint.config.js
const eslintPluginPrettierRecommended = require('eslint-plugin-prettier/recommended');

module.exports = [
  // Any other config imports go at the top
  eslintPluginPrettierRecommended,
];
Patch Changes

  • #​614 5270877 Thanks @​BPScott! - Add meta block to plugin. This improves debugging and cachebusting when using the new flat config

  • #​603 a63a570 Thanks @​filiptammergard! - fix: specify eslint-config-prettier as peer dependency

    It's already added to peerDependenciesMeta as optional, which means it should also be specified in peerDependencies.

ota-meshi/eslint-plugin-yml (eslint-plugin-yml)

v1.11.0

Compare Source

Minor Changes
jantimon/html-webpack-plugin (html-webpack-plugin)

v5.6.0

Compare Source

Features
  • add @rspack/core as an optional peer dependency (#​1829) (56ff3ae)
  • Added support type=systemjs-module via the scriptLoading option (#​1822) (7effc30)
Bug Fixes
5.5.4 (2023-12-06)
Bug Fixes
5.5.3 (2023-06-10)
Bug Fixes
5.5.2 (2023-06-08)
Bug Fixes
5.5.1 (2023-04-15)
Bug Fixes
  • perf: defer loading of pretty-error to improve startup time (#​1789) (988709d)
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 {};
remix-run/react-router (react-router-dom)

v6.21.1

Compare Source

Patch Changes
  • Updated dependencies:
    • react-router@6.21.1
    • @remix-run/router@1.14.1

v6.21.0

Compare Source

Minor Changes

  • Add a new future.v7_relativeSplatPath flag to implement a breaking bug fix to relative routing when inside a splat route. (#​11087)

    This fix was originally added in #​10983 and was later reverted in #​11078 because it was determined that a large number of existing applications were relying on the buggy behavior (see #​11052)

    The Bug
    The buggy behavior is that without this flag, the default behavior when resolving relative paths is to ignore any splat (*) portion of the current route path.

    The Background
    This decision was originally made thinking that it would make the concept of nested different sections of your apps in <Routes> easier if relative routing would replace the current splat:

    <BrowserRouter>
  <Routes>
    <Route path="/" element={<Home />} />
    <Route path="dashboard/*" element={<Dashboard />} />
  </Routes>
</BrowserRouter>

    Any paths like /dashboard, /dashboard/team, /dashboard/projects will match the Dashboard route. The dashboard component itself can then render nested <Routes>:

    function Dashboard() {
  return (
    <div>
      <h2>Dashboard</h2>
      <nav>
        <Link to="/">Dashboard Home</Link>
        <Link to="team">Team</Link>
        <Link to="projects">Projects</Link>
      </nav>

      <Routes>
        <Route path="/" element={<DashboardHome />} />
        <Route path="team" element={<DashboardTeam />} />
        <Route path="projects" element={<DashboardProjects />} />
      </Routes>
    </div>
  );
}

    Now, all links and route paths are relative to the router above them. This makes code splitting and compartmentalizing your app really easy. You could render the Dashboard as its own independent app, or embed it into your large app without making any changes to it.

    The Problem

    The problem is that this concept of ignoring part of a path breaks a lot of other assumptions in React Router - namely that "." always means the current location pathname for that route. When we ignore the splat portion, we start getting invalid paths when using ".":

    // If we are on URL /dashboard/team, and we want to link to /dashboard/team:
function DashboardTeam() {
  // ❌ This is broken and results in <a href="/dashboard">
  return <Link to=".">A broken link to the Current URL</Link>;

  // ✅ This is fixed but super unintuitive since we're already at /dashboard/team!
  return <Link to="./team">A broken link to the Current URL</Link>;
}

    We've also introduced an issue that we can no longer move our DashboardTeam component around our route hierarchy easily - since it behaves differently if we're underneath a non-splat route, such as /dashboard/:widget. Now, our "." links will, properly point to ourself inclusive of the dynamic param value so behavior will break from it's corresponding usage in a /dashboard/* route.

    Even worse, consider a nested splat route configuration:

    <BrowserRouter>
  <Routes>
    <Route path="dashboard">
      <Route path="*" element={<Dashboard />} />
    </Route>
  </Routes>
</BrowserRouter>

    Now, a <Link to="."> and a <Link to=".."> inside the Dashboard component go to the same place! That is definitely not correct!

    Another common issue arose in Data Routers (and Remix) where any <Form> should post to it's own route action if you the user doesn't specify a form action:

    let router = createBrowserRouter({
  path: "/dashboard",
  children: [
    {
      path: "*",
      action: dashboardAction,
      Component() {
        // ❌ This form is broken!  It throws a 405 error when it submits because
        // it tries to submit to /dashboard (without the splat value) and the parent
        // `/dashboard` route doesn't have an action
        return <Form method="post">...</Form>;
      },
    },
  ],
});

    This is just a compounded issue from the above because the default location for a Form to submit to is itself (".") - and if we ignore the splat portion, that now resolves to the parent route.

    The Solution
    If you are leveraging this behavior, it's recommended to enable the future flag, move your splat to it's own route, and leverage ../ for any links to "sibling" pages:

    <BrowserRouter>
  <Routes>
    <Route path="dashboard">
      <Route index path="*" element={<Dashboard />} />
    </Route>
  </Routes>
</BrowserRouter>

function Dashboard() {
  return (
    <div>
      <h2>Dashboard</h2>
      <nav>
        <Link to="..">Dashboard Home</Link>
        <Link to="../team">Team</Link>
        <Link to="../projects">Projects</Link>
      </nav>

      <Routes>
        <Route path="/" element={<DashboardHome />} />
        <Route path="team" element={<DashboardTeam />} />
        <Route path="projects" element={<DashboardProjects />} />
      </Router>
    </div>
  );
}

    This way, . means "the full current pathname for my route" in all cases (including static, dynamic, and splat routes) and .. always means "my parents pathname".

Patch Changes
  • Updated dependencies:
    • @remix-run/router@1.14.0
    • react-router@6.21.0
tailwindlabs/tailwindcss (tailwindcss)

v3.4.0

Compare Source

Added
  • Add svh, lvh, and dvh values to default height/min-height/max-height theme (#​11317)
  • Add has-* variants for :has(...) pseudo-class (#​11318)
  • Add text-wrap utilities including text-balance and text-pretty (#​11320, #​12031)
  • Extend default opacity scale to include all steps of 5 (#​11832)
  • Update Preflight html styles to include shadow DOM :host pseudo-class (#​11200)
  • Increase default values for grid-rows-* utilities from 1–6 to 1–12 (#​12180)
  • Add size-* utilities (#​12287)
  • Add utilities for CSS subgrid (#​12298)
  • Add spacing scale to min-w-*, min-h-*, and max-w-* utilities (#​12300)
  • Add forced-color-adjust utilities (#​11931)
  • Add forced-colors variant (#​11694, #​12582)
  • Add appearance-auto utility (#​12404)
  • Add logical property values for float and clear utilities (#​12480)
  • Add * variant for targeting direct children (#​12551)
Changed
  • Simplify the sans font-family stack (#​11748)
  • Disable the tap highlight overlay on iOS (#​12299)
  • Improve relative precedence of rtl, ltr, forced-colors, and dark variants (#​12584)

v3.3.7

Compare Source

Fixed
  • Fix support for container query utilities with arbitrary values (#​12534)
  • Fix custom config loading in Standalone CLI (#​12616)

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 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 added the dependencies Pull requests that update a dependency file label Dec 22, 2023
@codecov Codecov
Copy link

codecov bot commented Dec 22, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (34d4d91) 100.00% compared to head (ceb099d) 100.00%.

Additional details and impacted files 
@@            Coverage Diff            @@
##              main     #1072   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            8         8           
  Lines           57        57           
  Branches         2         2           
=========================================
  Hits            57        57

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

@pull-request-quantifier-deprecated Pull Request Quantifier (deprecated)
Copy link

This PR has 50 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

Quantification details 

Label      : Extra Small
Size       : +25 -25
Percentile : 20%

Total files changed: 10

Change summary by file extension:
.json : +25 -25
.lock : +0 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detected.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

@socket-security Socket Security
Copy link

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Packages Version New capabilities Transitives Size Publisher
@easyops-cn/docusaurus-search-local 0.38.1...0.40.0 None +6/-6 8.14 MB easyops-eve
react-router-dom 6.20.1...6.21.1 None +0/-0 864 kB mjackson
tailwindcss 3.3.6...3.4.0 None +0/-0 5.58 MB adamwathan

@renovate renovate bot merged commit 3373cc7 into main Dec 22, 2023
12 checks passed
@renovate renovate bot deleted the renovate/dependencies branch December 22, 2023 21:25
github-actions bot added a commit that referenced this pull request Dec 22, 2023
@github-actions
fix(deps): update dependencies (non-major) (#1072)
0399e16 
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> 3373cc7
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
dependencies Pull requests that update a dependency file Extra Small
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants