Update npm non-major dependencies #671

renovate · 2023-12-21T04:34:37Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@navikt/aksel-icons (source)	`5.11.4` -> `5.12.4`
@types/react (source)	`18.2.43` -> `18.2.46`
@types/react-dom (source)	`18.2.17` -> `18.2.18`
@typescript-eslint/parser (source)	`6.14.0` -> `6.17.0`
axios (source)	`1.6.2` -> `1.6.4`
classnames	`2.3.2` -> `2.5.1`
cypress (source)	`13.6.1` -> `13.6.2`
eslint (source)	`8.55.0` -> `8.56.0`
eslint-plugin-import	`2.29.0` -> `2.29.1`
eslint-plugin-n	`16.3.1` -> `16.6.1`
eslint-plugin-prettier	`5.0.1` -> `5.1.2`
i18next (source)	`23.7.8` -> `23.7.16`
prettier (source)	`3.1.0` -> `3.1.1`
react-router-dom (source)	`6.20.1` -> `6.21.1`

Release Notes

navikt/aksel (@navikt/aksel-icons)

Minor Changes

Ikoner: Oppdatert ikonpakke med diverse bugdfixes og oppdateringer av stroke (#2538)

`v5.11.5`

Compare Source

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

`v6.17.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.16.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.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.

axios/axios (axios)

`v1.6.4`

Compare Source

Bug Fixes

security: fixed formToJSON prototype pollution vulnerability; (#6167) (3c0c11c)
security: fixed security vulnerability in follow-redirects (#6163) (75af1cd)

Contributors to this release

`v1.6.3`

Compare Source

Bug Fixes

Regular Expression Denial of Service (ReDoS) (#6132) (5e7ad38)

Contributors to this release

JedWatson/classnames (classnames)

`v2.5.1`

Compare Source

Remove workspaces field from package (#350)

`v2.5.0`

Compare Source

Restore ability to pass a TypeScript interface (#341)
Add exports field to package (#342)

`v2.4.0`

Compare Source

Use string concatenation to increase performance thanks Jon Koops (#336)

`v2.3.3`

Compare Source

Fix default export, thanks Remco Haszing (#301)
Fix types for read-only arrays, thanks Ben Thompson (#307)
Replace README examples with functional-style components, thanks JoeDGit (#303)

cypress-io/cypress (cypress)

`v13.6.2`

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#13-6-2

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

ba6af85 chore: upgrade @eslint/js @8.56.0 (#17864) (Milos Djermanovic)
60a531a chore: package.json update for @eslint/js release (Jenkins)
ba87a06 chore: update dependency markdownlint to ^0.32.0 (#17783) (renovate[bot])
9271d10 chore: add GitHub issue template for docs issues (#17845) (Josh Goldberg ✨)
70a686b chore: Convert rule tests to FlatRuleTester (#17819) (Nicholas C. Zakas)
f3a599d chore: upgrade eslint-plugin-unicorn to v49.0.0 (#17837) (唯然)
905d4b7 chore: upgrade eslint-plugin-eslint-plugin v5.2.1 (#17838) (唯然)
4d7c3ce chore: update eslint-plugin-n v16.4.0 (#17836) (唯然)
fd0c60c ci: unpin Node.js 21.2.0 (#17821) (Francesco Trotta)

import-js/eslint-plugin-import (eslint-plugin-import)

`v2.29.1`

Compare Source

Fixed

[no-extraneous-dependencies]: ignore export type { ... } from '...' when includeTypes is false ([#2919], thanks [@Pandemic1617])
[no-unused-modules]: support export patterns with array destructuring ([#2930], thanks [@ljharb])
[Deps] update tsconfig-paths ([#2447], thanks [@domdomegg])

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

`v16.6.1`

Compare Source

fix: eslint 7.0 support (#156) (2419888)

`v16.6.0`

Compare Source

feat: supported new globals added in the new node.js versions (#154) (7628925)

`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

feat: eslint v9.0.0 compatibility (fixes #143) (#144) (b075568)
docs: add playground (fixes #25) (#145) (8bd6c7e)

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

`v5.1.2`

Compare Source

Patch Changes

#623 8210e44 Thanks @BPScott! - Add exports mapping to package.json, to allow import eslintPluginRecommended from 'eslint-plugin-prettier/recommended' to work as expected.

Strictly speaking this is a breaking change as it removes the ability for people to import from "eslint-plugin-prettier/eslint-plugin-prettier.js" and "eslint-plugin-prettier/recommended.js" but the former was never recommended in the first place and the latter has only been available for a few days.
#621 2b09e7f Thanks @JounQin! - feat: support parsing markdown via eslint-mdx natively

`v5.1.1`

Compare Source

Patch Changes

#619 b5c0dc5 Thanks @JounQin! - chore: skip formatting inline scripts in pug files

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

i18next/i18next (i18next)

`v23.7.16`

Compare Source

fix: Use Typescript 5 types with Typescript 5+ 2108
- Hint: If you're using TypeScript 4 and you navigate to the type definitions in your code editor, it might be you will see the TypeScript 5 types, but the TS compiler should use the correct types.

`v23.7.15`

Compare Source

types: simplifies types for array access and fixes 2103

`v23.7.14`

Compare Source

types: fix types for array access

`v23.7.13`

Compare Source

types: optimise ParseTReturn 2095

`v23.7.12`

Compare Source

types: fix for older ts version (context validation only for TS 5)

`v23.7.11`

Compare Source

types: fix for older ts versions 2090

`v23.7.10`

Compare Source

types: initializedStoreOnce and initializedLanguageOnce 2089

`v23.7.9`

Compare Source

types: fix FormatFunction should allow any value inside options parameter

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

Configuration

📅 Schedule: Branch creation - "before 07:00 on Thursday" in timezone Europe/Oslo, 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.

github-actions bot added the dependencies Pull request for dependency change label Dec 21, 2023

renovate bot force-pushed the renovate/npm-minor-patch branch 6 times, most recently from 8e36b3d to 2960ce0 Compare December 28, 2023 18:53

renovate bot force-pushed the renovate/npm-minor-patch branch 7 times, most recently from 49f9b31 to 1dc9d2c Compare January 4, 2024 19:56

renovate bot force-pushed the renovate/npm-minor-patch branch 6 times, most recently from be9e5e1 to bca50e6 Compare January 8, 2024 15:16

Update npm non-major dependencies

549a79a

renovate bot force-pushed the renovate/npm-minor-patch branch from bca50e6 to 549a79a Compare January 8, 2024 15:21

allinox approved these changes Jan 8, 2024

View reviewed changes

allinox merged commit 10a61e4 into main Jan 8, 2024
2 checks passed

allinox deleted the renovate/npm-minor-patch branch January 8, 2024 15:32

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update npm non-major dependencies #671

Update npm non-major dependencies #671

renovate bot commented Dec 21, 2023 •

edited

Loading

Update npm non-major dependencies #671

Update npm non-major dependencies #671

Conversation

renovate bot commented Dec 21, 2023 • edited Loading

Release Notes

Minor Changes

Bug Fixes

Contributors to this release

Bug Fixes

Contributors to this release

Features

Bug Fixes

Documentation

Chores

Fixed

Features

Docs & Chores

Patch Changes

Patch Changes

Minor Changes

Patch Changes

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

Skip explicitly passed symbolic links with --no-error-on-unmatched-pattern (#​15533 by @​sanmai-NL)

Consistently use tabs in ternaries when useTabs is true (#​15662 by @​auvred)

Improve config file search (#​15663 by @​fisker)

Fix unstable and ugly formatting for comments in destructuring patterns (#​15708 by @​sosukesuzuki)

Support "Import Attributes" (#​15718 by @​fisker)

Fix false claim in docs that cursorOffset is incompatible with rangeStart/rangeEnd (#​15750 by @​ExplodingCabbage)

Keep curly braces and from keyword in empty import statements (#​15756 by @​fisker)

Keep empty import attributes and assertions (#​15757 by @​fisker)

Patch Changes

Minor Changes

Patch Changes

Configuration

renovate bot commented Dec 21, 2023 •

edited

Loading

Fix config file search (#15363 by @fisker)

Skip explicitly passed symbolic links with `--no-error-on-unmatched-pattern` (#15533 by @sanmai-NL)

Consistently use tabs in ternaries when `useTabs` is `true` (#15662 by @auvred)

Improve config file search (#15663 by @fisker)

Fix unstable and ugly formatting for comments in destructuring patterns (#15708 by @sosukesuzuki)

Support "Import Attributes" (#15718 by @fisker)

Fix false claim in docs that cursorOffset is incompatible with rangeStart/rangeEnd (#15750 by @ExplodingCabbage)

Keep curly braces and `from` keyword in empty `import` statements (#15756 by @fisker)

Keep empty import attributes and assertions (#15757 by @fisker)