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

Merged
merged 1 commit into from
Jul 31, 2023
Merged

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

merged 1 commit into from
Jul 31, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 31, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@types/node (source) ^20.4.4 -> ^20.4.5 age adoption passing confidence
@typescript-eslint/eslint-plugin ^6.1.0 -> ^6.2.0 age adoption passing confidence
@typescript-eslint/parser ^6.1.0 -> ^6.2.0 age adoption passing confidence
esbuild ^0.18.16 -> ^0.18.17 age adoption passing confidence
eslint (source) ^8.45.0 -> ^8.46.0 age adoption passing confidence
eslint-config-prettier ^8.8.0 -> ^8.9.0 age adoption passing confidence
pnpm (source) 8.6.10 -> 8.6.11 age adoption passing confidence
rollup (source) ^3.26.3 -> ^3.27.0 age adoption passing confidence

Release Notes

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

v6.2.0

Compare Source

Bug Fixes
  • eslint-plugin: [member-ordering] account for repeated names (#​6864) (d207b59)
  • eslint-plugin: [no-unsafe-enum-comparison] exempt bit shift operators (#​7074) (b3e0e75)
  • eslint-plugin: [prefer-nullish-coalescing] handle case when type of left side is null or undefined (#​7225) (b62affe)
  • eslint-plugin: use a default export for the rules type (#​7266) (af77a1d)
Features
  • eslint-plugin: [class-methods-use-this] add extension rule (#​6457) (18ea3b1)
  • eslint-plugin: sync getFunctionHeadLoc implementation with upstream (#​7260) (f813147)

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

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

v6.2.0

Compare Source

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

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

evanw/esbuild (esbuild)

v0.18.17

Compare Source

  • Support An+B syntax and :nth-*() pseudo-classes in CSS

    This adds support for the :nth-child(), :nth-last-child(), :nth-of-type(), and :nth-last-of-type() pseudo-classes to esbuild, which has the following consequences:

    • The An+B syntax is now parsed, so parse errors are now reported
    • An+B values inside these pseudo-classes are now pretty-printed (e.g. a leading + will be stripped because it's not in the AST)
    • When minification is enabled, An+B values are reduced to equivalent but shorter forms (e.g. 2n+0 => 2n, 2n+1 => odd)
    • Local CSS names in an of clause are now detected (e.g. in :nth-child(2n of :local(.foo)) the name foo is now renamed)
    /* Original code */
.foo:nth-child(+2n+1 of :local(.bar)) {
  color: red;
}

/* Old output (with --loader=local-css) */
.stdin_foo:nth-child(+2n + 1 of :local(.bar)) {
  color: red;
}

/* New output (with --loader=local-css) */
.stdin_foo:nth-child(2n+1 of .stdin_bar) {
  color: red;
}

  • Adjust CSS nesting parser for IE7 hacks (#​3272)

    This fixes a regression with esbuild's treatment of IE7 hacks in CSS. CSS nesting allows selectors to be used where declarations are expected. There's an IE7 hack where prefixing a declaration with a * causes that declaration to only be applied in IE7 due to a bug in IE7's CSS parser. However, it's valid for nested CSS selectors to start with *. So esbuild was incorrectly parsing these declarations and anything following it up until the next { as a selector for a nested CSS rule. This release changes esbuild's parser to terminate the parsing of selectors for nested CSS rules when a ; is encountered to fix this edge case:

    /* Original code */
.item {
  *width: 100%;
  height: 1px;
}

/* Old output */
.item {
  *width: 100%; height: 1px; {
  }
}

/* New output */
.item {
  *width: 100%;
  height: 1px;
}

    Note that the syntax for CSS nesting is about to change again, so esbuild's CSS parser may still not be completely accurate with how browsers do and/or will interpret CSS nesting syntax. Expect additional updates to esbuild's CSS parser in the future to deal with upcoming CSS specification changes.

  • Adjust esbuild's warning about undefined imports for TypeScript import equals declarations (#​3271)

    In JavaScript, accessing a missing property on an import namespace object is supposed to result in a value of undefined at run-time instead of an error at compile-time. This is something that esbuild warns you about by default because doing this can indicate a bug with your code. For example:

    // app.js
import * as styles from './styles'
console.log(styles.buton)
    // styles.js
export let button = {}

    If you bundle app.js with esbuild you will get this:

    ▲ [WARNING] Import "buton" will always be undefined because there is no matching export in "styles.js" [import-is-undefined]

    app.js:2:19:
      2 │ console.log(styles.buton)
        │                    ~~~~~
        ╵                    button

  Did you mean to import "button" instead?

    styles.js:1:11:
      1 │ export let button = {}
        ╵            ~~~~~~

    However, there is TypeScript-only syntax for import equals declarations that can represent either a type import (which esbuild should ignore) or a value import (which esbuild should respect). Since esbuild doesn't have a type system, it tries to only respect import equals declarations that are actually used as values. Previously esbuild always generated this warning for unused imports referenced within import equals declarations even when the reference could be a type instead of a value. Starting with this release, esbuild will now only warn in this case if the import is actually used. Here is an example of some code that no longer causes an incorrect warning:

    // app.ts
import * as styles from './styles'
import ButtonType = styles.Button
    // styles.ts
export interface Button {}
eslint/eslint (eslint)

v8.46.0

Compare Source

Features

Bug Fixes

  • 9803c7c fix: FlatESLint#getRulesMetaForResults shouldn't throw on unknown rules (#​17393) (Milos Djermanovic)
  • 42faa17 fix: Update no-loop-func to not overlap with no-undef (#​17358) (Matt Wilkinson)

Documentation

  • 4d474e3 docs: update with TypeScript info (#​17423) (James)
  • 091f44e docs: File extension named processor deprecation (#​17362) (Matt Wilkinson)
  • 9254a6c docs: Update README (GitHub Actions Bot)
  • 6d6dc51 docs: fix overlapping of open in playground button (#​17403) (Tanuj Kanti)
  • 7fc3a2c docs: Add private class features info to no-underscore-dangle (#​17386) (Matt Wilkinson)
  • da73e58 docs: Migrating eslint-env configuration comments (#​17390) (Francesco Trotta)
  • 80dffed docs: fix Ignoring Files section in config migration guide (#​17392) (Milos Djermanovic)
  • 8a9abb7 docs: Update README (GitHub Actions Bot)
  • 7e9be4b docs: Update README (GitHub Actions Bot)
  • 0b0bbe0 docs: Update README (GitHub Actions Bot)

Chores

  • d1eb7e4 chore: Update ecosystem dependencies (#​17427) (Nicholas C. Zakas)
  • fab9e97 chore: package.json update for eslint-config-eslint release (ESLint Jenkins)
  • 6246711 chore: package.json update for @​eslint/js release (ESLint Jenkins)
  • 0aa0bc3 chore: Add PRs to triage project (#​17421) (Nicholas C. Zakas)
prettier/eslint-config-prettier (eslint-config-prettier)

v8.9.0

Compare Source

  • Added: [vue/array-element-newline]. Thanks to @​xcatliu!
pnpm/pnpm (pnpm)

v8.6.11

Compare Source

Patch Changes

  • Change the install error message when a lockfile is wanted but absent to indicate the wanted lockfile is absent, not present. This now reflects the actual error #​6851.
  • When dealing with a local dependency that is a path to a symlink, a new symlink should be created to the original symlink, not to the actual directory location.
  • The length of the temporary file names in the content-addressable store reduced in order to prevent ENAMETOOLONG errors from happening #​6842.
  • Don't print "added" stats, when installing with --lockfile-only.
  • Installation of a git-hosted dependency should not fail if the pnpm-lock.yaml file of the installed dependency is not up-to-date #​6865.
  • Don't ignore empty strings in params #​6594.
  • Always set dedupe-peer-dependents to false, when running installation during deploy #​6858.
  • When several containers use the same store simultaneously, there's a chance that multiple containers may create a temporary file at the same time. In such scenarios, pnpm could fail to rename the temporary file in one of the containers. This issue has been addressed: pnpm will no longer fail if the temporary file is absent but the destination file exists.
  • Authorization token should be found in the configuration, when the requested URL is explicitly specified with a default port (443 on HTTPS or 80 on HTTP) #​6863.

Our Gold Sponsors

Our Silver Sponsors
rollup/rollup (rollup)

v3.27.0

Compare Source

2023-07-28

Features
  • Mark Object.values and Object.entries as pure if their argument does not contain getters (#​5072)
Pull Requests

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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.

@AriPerkkio AriPerkkio merged commit 868500e into master Jul 31, 2023
12 checks passed
@AriPerkkio AriPerkkio deleted the renovate/all-minor-patch branch July 31, 2023 03:55
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
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@AriPerkkio