Skip to content
This repository has been archived by the owner on Apr 19, 2023. It is now read-only.

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 16, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) 18.11.17 -> 18.15.11 age adoption passing confidence
eslint (source) 8.30.0 -> 8.37.0 age adoption passing confidence
pnpm (source) 7.18.2 -> 7.30.5 age adoption passing confidence
typescript (source) 4.9.4 -> 4.9.5 age adoption passing confidence
vitest 0.26.1 -> 0.29.8 age adoption passing confidence

Release Notes

eslint/eslint

v8.37.0

Compare Source

Features

Bug Fixes

  • 619f3fd fix: correctly handle null default config in RuleTester (#​17023) (Brad Zacher)
  • 1fbf118 fix: getFirstToken/getLastToken on comment-only node (#​16889) (Francesco Trotta)
  • 129e252 fix: Fix typo in logical-assignment-operators rule description (#​17000) (Francesco Trotta)

Documentation

Chores

v8.36.0

Compare Source

Features

Bug Fixes

  • 92c1943 fix: correctly iterate files matched by glob patterns (#​16831) (Nitin Kumar)

Documentation

  • b98fdd4 docs: Update README (GitHub Actions Bot)
  • caf08ce docs: fix estree link in custom formatters docs (#​16967) (Milos Djermanovic)
  • 3398431 docs: Custom Parsers cleanup/expansion (#​16887) (Ben Perlmutter)
  • 19d3531 docs: Update README (GitHub Actions Bot)
  • b09a512 docs: detect and fix broken links (#​16837) (Nitin Kumar)

Chores

v8.35.0

Compare Source

Features

  • 8e34a04 feat: add afterHashbangComment option to lines-around-comment rule (#​16920) (SUZUKI Sosuke)
  • c8c0c71 feat: Move all and recommended configs into package. (#​16844) (Nicholas C. Zakas)
  • 71f6f0d feat: report more cases with ?? in no-constant-binary-expression (#​16826) (Daiki Nishikawa)

Bug Fixes

Documentation

Chores

v8.34.0

Compare Source

Features

  • 9b2fcf7 feat: array-callback-return supports Array.prototype.toSorted (#​16845) (SUZUKI Sosuke)

Bug Fixes

  • 923f61d fix: false positive with assignment in no-extra-parens (#​16872) (Francesco Trotta)

Documentation

Chores

v8.33.0

Compare Source

Features

  • 2cc7954 feat: add restrictDefaultExports option to no-restricted-exports rule (#​16785) (Nitin Kumar)

Documentation

  • 17f4be2 docs: Fix examples in no-multiple-empty-lines rule (#​16835) (jonz94)
  • 9c7cfe3 docs: 'Source Code' content in 'Set up Development Environment' page (#​16780) (Ben Perlmutter)
  • ede5c64 docs: Custom processors page (#​16802) (Ben Perlmutter)
  • 2620614 docs: Code of Conduct page (#​16781) (Ben Perlmutter)
  • 50a8efd docs: report a sec vulnerability page (#​16808) (Ben Perlmutter)
  • ed60afd docs: Update page titles, section landing pages, and side TOC (#​16760) (Ben Perlmutter)
  • 333c712 docs: add background to code-path-diagrams for dark-mode (#​16822) (Tanuj Kanti)
  • f5f7b9b docs: Update README (GitHub Actions Bot)
  • 2aa4f5f docs: no-constant-condition: Add multi-comparison example (#​16776) (Sebastian Simon)
  • 40287db docs: Remove Google Group icon (#​16779) (Nicholas C. Zakas)
  • ea10ca5 docs: 'a .eslint' -> 'an .eslint' for consistency (#​16809) (Ben Perlmutter)
  • 3be0748 docs: add example for nodejs lintText api (#​16789) (Siva K)
  • ce4f5ff docs: Replace removed related rules with a valid rule (#​16800) (Ville Saalo)

v8.32.0

Compare Source

Features

  • fc20f24 feat: add suggestions for redundant wrapping in prefer-regex-literals (#​16658) (YeonJuan)

Bug Fixes

Documentation

  • 17b65ad docs: IA Update page URL move (#​16665) (Ben Perlmutter)
  • 5981296 docs: fix theme switcher button (#​16752) (Sam Chen)
  • 6669413 docs: deploy prerelease docs under the /docs/next/ path (#​16541) (Nitin Kumar)
  • 78ecfe0 docs: use inline code for rule options name (#​16768) (Percy Ma)
  • fc2ea59 docs: Update README (GitHub Actions Bot)
  • 762a872 docs: Update README (GitHub Actions Bot)

Chores

  • 2952d6e chore: sync templates/*.md files with issue templates (#​16758) (gfyoung)
  • 3e34418 chore: Add new issues to triage project (#​16740) (Nicholas C. Zakas)

v8.31.0

Compare Source

Features

  • 52c7c73 feat: check assignment patterns in no-underscore-dangle (#​16693) (Milos Djermanovic)
  • b401cde feat: add options to check destructuring in no-underscore-dangle (#​16006) (Morten Kaltoft)
  • 30d0daf feat: group properties with values in parentheses in key-spacing (#​16677) (Francesco Trotta)

Bug Fixes

  • 35439f1 fix: correct syntax error in prefer-arrow-callback autofix (#​16722) (Francesco Trotta)
  • 87b2470 fix: new instance of FlatESLint should load latest config file version (#​16608) (Milos Djermanovic)

Documentation

Chores

pnpm/pnpm

v7.30.5

Compare Source

Patch Changes

  • pnpm audit should work even if there are no package.json file, just a pnpm-lock.yaml file.
  • Dedupe direct dependencies after hoisting.
  • Don't remove automatically installed peer dependencies from the root workspace project, when dedupe-peer-dependents is true #​6154.

Our Gold Sponsors

Our Silver Sponsors

v7.30.4

Compare Source

v7.30.3

Compare Source

Patch Changes

  • Should use most specific override rule when multiple rules match the same target #​6210.
  • Fix regression introduced in v7.30.1 #​6271.

Our Gold Sponsors

Our Silver Sponsors

v7.30.2

Compare Source

v7.30.1

Compare Source

Patch Changes

  • Don't write the pnpm-lock.yaml file if it has no changes and pnpm install --frozen-lockfile was executed #​6158.
  • Fix git-hosted dependencies referenced via git+ssh that use semver selectors #​6239.
  • When publish some package throws an error, the exit code should be non-zero #​5528.
  • Only three paths are displayed in pnpm audit output #​6203
  • Aliased packages should be used to resolve peer dependencies too #​4301.

Our Gold Sponsors

Our Silver Sponsors

v7.30.0

Compare Source

Minor Changes

  • Allow to set a custom directory for storing patch files via the patches-dir setting #​6215

Patch Changes

  • New directories should be prepended to NODE_PATH in command shims, not appended.
  • Retry copying file on EBUSY error #​6201.

Our Gold Sponsors

Our Silver Sponsors

v7.29.3

Compare Source

Patch Changes

  • Command shim should not set higher priority to the node_modules/.pnpm/node_modules directory through the NODE_PATH env variable, then the command's own node_modules directory #​5176.
  • extend-node-path is set back to true by default. It was set to false in v7.29.2 in order to fix issues with multiple versions of Jest in one workspace. It has caused other issues, so now we keep extending NODE_PATH. We have fixed the Jest issue with a different solution #​6213.

Our Gold Sponsors

Our Silver Sponsors

v7.29.2

Compare Source

v7.29.1

Compare Source

Patch Changes

  • Settings related to authorization should be set/deleted by npm CLI #​6181.

Our Gold Sponsors

Our Silver Sponsors

v7.29.0

Compare Source

Minor Changes

  • A new setting is now supported: dedupe-peer-dependents.

    When this setting is set to true, packages with peer dependencies will be deduplicated after peers resolution.

    For instance, let's say we have a workspace with two projects and both of them have webpack in their dependencies. webpack has esbuild in its optional peer dependencies, and one of the projects has esbuild in its dependencies. In this case, pnpm will link two instances of webpack to the node_modules/.pnpm directory: one with esbuild and another one without it:

    node_modules
      .pnpm
        webpack@1.0.0_esbuild@1.0.0
        webpack@1.0.0
    project1
      node_modules
        webpack -> ../../node_modules/.pnpm/webpack@1.0.0/node_modules/webpack
    project2
      node_modules
        webpack -> ../../node_modules/.pnpm/webpack@1.0.0_esbuild@1.0.0/node_modules/webpack
        esbuild
    

    This makes sense because webpack is used in two projects, and one of the projects doesn't have esbuild, so the two projects cannot share the same instance of webpack. However, this is not what most developers expect, especially since in a hoisted node_modules, there would only be one instance of webpack. Therefore, you may now use the dedupe-peer-dependents setting to deduplicate webpack when it has no conflicting peer dependencies (explanation at the end). In this case, if we set dedupe-peer-dependents to true, both projects will use the same webpack instance, which is the one that has esbuild resolved:

    node_modules
      .pnpm
        webpack@1.0.0_esbuild@1.0.0
    project1
      node_modules
        webpack -> ../../node_modules/.pnpm/webpack@1.0.0_esbuild@1.0.0/node_modules/webpack
    project2
      node_modules
        webpack -> ../../node_modules/.pnpm/webpack@1.0.0_esbuild@1.0.0/node_modules/webpack
        esbuild
    

    What are conflicting peer dependencies? By conflicting peer dependencies we mean a scenario like the following one:

    node_modules
      .pnpm
        webpack@1.0.0_react@16.0.0_esbuild@1.0.0
        webpack@1.0.0_react@17.0.0
    project1
      node_modules
        webpack -> ../../node_modules/.pnpm/webpack@1.0.0/node_modules/webpack
        react (v17)
    project2
      node_modules
        webpack -> ../../node_modules/.pnpm/webpack@1.0.0_esbuild@1.0.0/node_modules/webpack
        esbuild
        react (v16)
    

    In this case, we cannot dedupe webpack as webpack has react in its peer dependencies and react is resolved from two different versions in the context of the two projects.

Patch Changes

  • The configuration added by pnpm setup should check if the pnpm home directory is already in the PATH before adding to the PATH.

    Before this change, this code was added to the shell:

    export PNPM_HOME="$HOME/Library/pnpm"
    export PATH="$PNPM_HOME:$PATH"

    Now this will be added:

    export PNPM_HOME="$HOME/Library/pnpm"
    case ":$PATH:" in
      *":$PNPM_HOME:"*) ;;
      *) export PATH="$PNPM_HOME:$PATH" ;;
    esac
  • Add skipped status in exec report summary when script is missing #​6139.

  • pnpm env -g should fail with a meaningful error message if pnpm cannot find the pnpm home directory, which is the directory into which Node.js is installed.

  • Should not throw an error when local dependency use file protocol #​6115.

  • Fix the incorrect error block when subproject has been patched #​6183

Our Gold Sponsors

Our Silver Sponsors

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 4 times, most recently from cbb2de3 to c842064 Compare January 23, 2023 11:46
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from 3341a5a to e42c3c8 Compare January 30, 2023 23:42
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 3b6f27c to 3c17aec Compare February 7, 2023 11:54
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from e90429b to b79de43 Compare February 13, 2023 15:39
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 93928db to bd6866f Compare February 23, 2023 11:42
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from 6ae553c to d67b3ff Compare March 4, 2023 04:40
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 9792966 to 66cdb69 Compare March 11, 2023 01:14
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from d8bf096 to 46abf62 Compare March 16, 2023 09:01
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 46abf62 to cc14759 Compare April 3, 2023 16:23
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from cc14759 to 99d3229 Compare April 17, 2023 12:02
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 99d3229 to aad8f52 Compare April 18, 2023 02:57
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants