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

Merged
merged 1 commit into from Jun 1, 2022
Merged

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

merged 1 commit into from Jun 1, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 16, 2022 •
edited

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@typescript-eslint/eslint-plugin ^5.23.0 -> ^5.27.0 age adoption passing confidence
@typescript-eslint/parser ^5.23.0 -> ^5.27.0 age adoption passing confidence
esbuild 0.14.39 -> 0.14.42 age adoption passing confidence
eslint (source) ^8.15.0 -> ^8.16.0 age adoption passing confidence
lint-staged ^12.4.1 -> ^12.5.0 age adoption passing confidence
pnpm (source) 7.1.0 -> 7.1.7 age adoption passing confidence
postcss (source) ^8.4.13 -> ^8.4.14 age adoption passing confidence
typescript (source) ^4.6.4 -> ^4.7.2 age adoption passing confidence
vitest ^0.12.6 -> ^0.13.1 age adoption passing confidence

Release Notes

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

v5.27.0

Compare Source

Bug Fixes
  • eslint-plugin: [no-type-alias] handle Template Literal Types (#​5092) (8febf11)
Features
  • [4.7] support new extensions (#​5027) (efc147b)
  • eslint-plugin: [ban-ts-comment] add descriptionFormat option (#​5026) (1fb31a4)
  • eslint-plugin: [no-misused-promises] warn when spreading promises (#​5053) (61ffa9e)
  • eslint-plugin: [space-infix-ops] missing error report for conditional types (#​5041) (0bfab6c)

v5.26.0

Compare Source

Bug Fixes
  • eslint-plugin: [member-delimiter-style] autofixer result is not as expected when comments after the delimiter with option delimiter: 'none' (#​5029) (ed7b5f6)
  • eslint-plugin: [member-delimiter-style] autofixer result is not as expected with option delimiter: 'none' (#​5023) (9e97a11)
  • eslint-plugin: [prefer-readonly] correct issue with anonymus functions (#​4974) (952e2f0), closes #​2590

v5.25.0

Compare Source

Bug Fixes
  • eslint-plugin: [typedef] stop enforcing rule for assignment expressions (#​4958) (04a216c)
  • eslint-plugin: strict config should not extend recommended (#​5005) (05d71c2)
  • website: correct Presets link to be Configs (#​5004) (e18e91c)
Features
  • eslint-plugin: [no-empty-function] new allow option overrideMethods (#​4923) (13c05ae)
  • eslint-plugin: deprecate no-duplicate-imports in favour of import/no-duplicates (#​4973) (1d2e41a)
  • update to TypeScript 4.7-rc (#​4829) (6fe783c)

v5.24.0

Compare Source

Bug Fixes
Features
typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v5.27.0

Compare Source

Bug Fixes
  • types: remove leftovers from removal of useJSXTextNode (#​5091) (f9c3647)
Features

v5.26.0

Compare Source

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

v5.25.0

Compare Source

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

v5.24.0

Compare Source

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

evanw/esbuild

v0.14.42

Compare Source

  • Fix a parser hang on invalid CSS (#​2276)

    Previously invalid CSS with unbalanced parentheses could cause esbuild's CSS parser to hang. An example of such an input is the CSS file :x(. This hang has been fixed.

  • Add support for custom log message levels

    This release allows you to override the default log level of esbuild's individual log messages. For example, CSS syntax errors are treated as warnings instead of errors by default because CSS grammar allows for rules containing syntax errors to be ignored. However, if you would like for esbuild to consider CSS syntax errors to be build errors, you can now configure that like this:

    • CLI

      $ esbuild example.css --log-override:css-syntax-error=error

    • JS API

      let result = await esbuild.build({
  entryPoints: ['example.css'],
  logOverride: {
    'css-syntax-error': 'error',
  },
})

    • Go API

      result := api.Build(api.BuildOptions{
  EntryPoints: []string{"example.ts"},
  LogOverride: map[string]api.LogLevel{
    "css-syntax-error": api.LogLevelError,
  },
})

    You can also now use this feature to silence warnings that you are not interested in. Log messages are referred to by their identifier. Each identifier is stable (i.e. shouldn't change over time) except there is no guarantee that the log message will continue to exist. A given log message may potentially be removed in the future, in which case esbuild will ignore log levels set for that identifier. The current list of supported log level identifiers for use with this feature can be found below:

    JavaScript:

    • assign-to-constant
    • call-import-namespace
    • commonjs-variable-in-esm
    • delete-super-property
    • direct-eval
    • duplicate-case
    • duplicate-object-key
    • empty-import-meta
    • equals-nan
    • equals-negative-zero
    • equals-new-object
    • html-comment-in-js
    • impossible-typeof
    • private-name-will-throw
    • semicolon-after-return
    • suspicious-boolean-not
    • this-is-undefined-in-esm
    • unsupported-dynamic-import
    • unsupported-jsx-comment
    • unsupported-regexp
    • unsupported-require-call

    CSS:

    • css-syntax-error
    • invalid-@​charset
    • invalid-@​import
    • invalid-@​nest
    • invalid-@​layer
    • invalid-calc
    • js-comment-in-css
    • unsupported-@​charset
    • unsupported-@​namespace
    • unsupported-css-property

    Bundler:

    • different-path-case
    • ignored-bare-import
    • ignored-dynamic-import
    • import-is-undefined
    • package.json
    • require-resolve-not-external
    • tsconfig.json

    Source maps:

    • invalid-source-mappings
    • sections-in-source-map
    • missing-source-map
    • unsupported-source-map-comment

    Documentation about which identifiers correspond to which log messages will be added in the future, but hasn't been written yet. Note that it's not possible to configure the log level for a build error. This is by design because changing that would cause esbuild to incorrectly proceed in the building process generate invalid build output. You can only configure the log level for non-error log messages (although you can turn non-errors into errors).

v0.14.41

Compare Source

  • Fix a minification regression in 0.14.40 (#​2270, #​2271, #​2273)

    Version 0.14.40 substituted string property keys with numeric property keys if the number has the same string representation as the original string. This was done in three places: computed member expressions, object literal properties, and class fields. However, negative numbers are only valid in computed member expressions while esbuild incorrectly applied this substitution for negative numbers in all places. This release fixes the regression by only doing this substitution for negative numbers in computed member expressions.

    This fix was contributed by @​susiwen8.

v0.14.40

Compare Source

  • Correct esbuild's implementation of "preserveValueImports": true (#​2268)

    TypeScript's preserveValueImports setting tells the compiler to preserve unused imports, which can sometimes be necessary because otherwise TypeScript will remove unused imports as it assumes they are type annotations. This setting is useful for programming environments that strip TypeScript types as part of a larger code transformation where additional code is appended later that will then make use of those unused imports, such as with Svelte or Vue.

    This release fixes an issue where esbuild's implementation of preserveValueImports diverged from the official TypeScript compiler. If the import clause is present but empty of values (even if it contains types), then the import clause should be considered a type-only import clause. This was an oversight, and has now been fixed:

    // Original code
import "keep"
import { k1 } from "keep"
import k2, { type t1 } from "keep"
import {} from "remove"
import { type t2 } from "remove"

// Old output under "preserveValueImports": true
import "keep";
import { k1 } from "keep";
import k2, {} from "keep";
import {} from "remove";
import {} from "remove";

// New output under "preserveValueImports": true (matches the TypeScript compiler)
import "keep";
import { k1 } from "keep";
import k2 from "keep";

  • Avoid regular expression syntax errors in older browsers (#​2215)

    Previously esbuild always passed JavaScript regular expression literals through unmodified from the input to the output. This is undesirable when the regular expression uses newer features that the configured target environment doesn't support. For example, the d flag (i.e. the match indices feature) is new in ES2022 and doesn't work in older browsers. If esbuild generated a regular expression literal containing the d flag, then older browsers would consider esbuild's output to be a syntax error and none of the code would run.

    With this release, esbuild now detects when an unsupported feature is being used and converts the regular expression literal into a new RegExp() constructor instead. One consequence of this is that the syntax error is transformed into a run-time error, which allows the output code to run (and to potentially handle the run-time error). Another consequence of this is that it allows you to include a polyfill that overwrites the RegExp constructor in older browsers with one that supports modern features. Note that esbuild does not handle polyfills for you, so you will need to include a RegExp polyfill yourself if you want one.

    // Original code
console.log(/b/d.exec('abc').indices)

// New output (with --target=chrome90)
console.log(/b/d.exec("abc").indices);

// New output (with --target=chrome89)
console.log(new RegExp("b", "d").exec("abc").indices);

    This is currently done transparently without a warning. If you would like to debug this transformation to see where in your code esbuild is transforming regular expression literals and why, you can pass --log-level=debug to esbuild and review the information present in esbuild's debug logs.

  • Add Opera to more internal feature compatibility tables (#​2247, #​2252)

    The internal compatibility tables that esbuild uses to determine which environments support which features are derived from multiple sources. Most of it is automatically derived from these ECMAScript compatibility tables, but missing information is manually copied from MDN, GitHub PR comments, and various other websites. Version 0.14.35 of esbuild introduced Opera as a possible target environment which was automatically picked up by the compatibility table script, but the manually-copied information wasn't updated to include Opera. This release fixes this omission so Opera feature compatibility should now be accurate.

    This was contributed by @​lbwa.

  • Ignore EPERM errors on directories (#​2261)

    Previously bundling with esbuild when inside a sandbox environment which does not have permission to access the parent directory did not work because esbuild would try to read the directory to search for a node_modules folder and would then fail the build when that failed. In practice this caused issues with running esbuild with sandbox-exec on macOS. With this release, esbuild will treat directories with permission failures as empty to allow for the node_modules search to continue past the denied directory and into its parent directory. This means it should now be possible to bundle with esbuild in these situations. This fix is similar to the fix in version 0.9.1 but is for EPERM while that fix was for EACCES.

  • Remove an irrelevant extra "use strict" directive (#​2264)

    The presence of a "use strict" directive in the output file is controlled by the presence of one in the entry point. However, there was a bug that would include one twice if the output format is ESM. This bug has been fixed.

  • Minify strings into integers inside computed properties (#​2214)

    This release now minifies a["0"] into a[0] when the result is equivalent:

    // Original code
console.log(x['0'], { '0': x }, class { '0' = x })

// Old output (with --minify)
console.log(x["0"],{"0":x},class{"0"=x});

// New output (with --minify)
console.log(x[0],{0:x},class{0=x});

    This transformation currently only happens when the numeric property represents an integer within the signed 32-bit integer range.

eslint/eslint

v8.16.0

Compare Source

Features

  • cab0c22 feat: add Unicode flag suggestion in no-misleading-character-class (#​15867) (Milos Djermanovic)
  • 38ae956 feat: check Unicode code point escapes in no-control-regex (#​15862) (Milos Djermanovic)
  • ee69cd3 feat: Update global variables (#​15871) (Sébastien Règne)

Bug Fixes

  • 3f09aab fix: function-paren-newline crash on "new new Foo();" (#​15850) (coderaiser)

Documentation

  • 050d5f4 docs: Static further reading links (#​15890) (Nicholas C. Zakas)
  • 36287c0 docs: fix absolute paths in related rules shortcode to work from /docs (#​15892) (Milos Djermanovic)
  • 90b6990 docs: fix absolute links in rule macro to work from /docs (#​15891) (Milos Djermanovic)
  • f437249 docs: Adjust docs site path prefix (#​15889) (Nicholas C. Zakas)
  • 6e16025 docs: update 'Related Rules' and 'Further Reading' in remaining rules (#​15884) (Milos Djermanovic)
  • 1d39f69 docs: remove confusing examples for no-mixed-operators (#​15875) (Milos Djermanovic)
  • 3071d76 docs: Fix some grammar issues (#​15837) (byodian)

Chores

okonet/lint-staged

v12.5.0

Compare Source

Bug Fixes
  • include all files when using --config <path> (641d1c2)
  • skip backup stash when using the --diff option (d4da24d)
Features
  • add --diff-filter option for overriding list of (staged) files (753ef72)
  • add --diff option for overriding list of (staged) files (35fcce9)

v12.4.3

Compare Source

Bug Fixes
  • deps: downgrade yaml@1.10.2 to support Node.js 12 (383a96e)
  • deps: update commander@^9.2.0 (22ebf52)
  • deps: update yaml@^2.0.1 (ec73af0)

v12.4.2

Compare Source

Bug Fixes
  • correctly handle --max-arg-length cli option (1db5f26)
pnpm/pnpm

v7.1.7

Compare Source

Patch Changes
  • Improve the performance of the build sequence calculation step #​4815.
  • Correctly detect repeated dependency sequence during resolution #​4813.
Our Sponsors
##### What's Changed * fix: `pnpm add @​teambit/bit` should succeed by @​zkochan in https://github.com/pnpm/pnpm/pull/4813 * perf: build-modules by @​zkochan in https://github.com/pnpm/pnpm/pull/4815

Full Changelog: pnpm/pnpm@v7.1.6...v7.1.7

v7.1.6

Compare Source

Patch Changes
  • Don't fail on projects with linked dependencies, when auto-install-peers is set to true #​4796.
  • NODE_ENV=production pnpm install --dev should only install dev deps #​4745.
Our Sponsors
##### What's Changed * fix: only devDependencies are installed regardless of the node env by @​Spencer17x in https://github.com/pnpm/pnpm/pull/4805 * fix(auto-install-peers): don't fail on projects with linked deps by @​zkochan in https://github.com/pnpm/pnpm/pull/4807

Full Changelog: pnpm/pnpm@v7.1.5...v7.1.6

v7.1.5

Compare Source

Patch Changes
  • Correctly detect the active Node.js version, when the pnpm CLI is bundled to an executable #​4203.
Our Sponsors

Full Changelog: pnpm/pnpm@v7.1.4...v7.1.5

v7.1.4

Compare Source

Patch Changes
  • Correctly detect the active Node.js version, when the pnpm CLI is bundled to an executable #​4203.
Our Sponsors
##### What's Changed * fix: correctly detect the active Node.js version by @​zkochan in https://github.com/pnpm/pnpm/pull/4780

Full Changelog: pnpm/pnpm@v7.1.3...v7.1.4

v7.1.3

Compare Source

Patch Changes

  • When auto-install-peers is set to true, automatically install missing peer dependencies without writing them to package.json as dependencies. This makes pnpm handle peer dependencies the same way as npm v7 #​4776.

Our Sponsors
#### What's Changed * chore: renovate bot setting to pin actions to a full length commit SHA by @​naveensrinivasan in https://github.com/pnpm/pnpm/pull/4768 * feat: auto install peer dependencies by @​zkochan in https://github.com/pnpm/pnpm/pull/4776 #### New Contributors * @​naveensrinivasan made their first contribution in https://github.com/pnpm/pnpm/pull/4768

Full Changelog: pnpm/pnpm@v7.1.2...v7.1.3

v7.1.2

Compare Source

Patch Changes

  • pnpm setup should not fail on Windows if PNPM_HOME is not yet in the system registry #​4757
  • pnpm dlx shouldn't modify the lockfile in the current working directory #​4743.

Our Sponsors
#### What's Changed * fix(setup): don't fail if PNPM_HOME is not yet in the system registry by @​zkochan in https://github.com/pnpm/pnpm/pull/4760 * fix(dlx): do not modify the lockfile in the cwd by @​zkochan in https://github.com/pnpm/pnpm/pull/4762

Full Changelog: pnpm/pnpm@v7.1.1...v7.1.2

v7.1.1

Compare Source

Patch Changes
  • When the global bin directory is set to a symlink, check not only the symlink in the PATH but also the target of the symlink #​4744.
  • Sanitize the directory names created inside node_modules/.pnpm and inside the global store #​4716
  • All arguments after pnpm create <pkg> should be passed to the executed create app package. So pnpm create next-app --typescript should work`.
  • Resolve commits from GitHub via https #​4734.
Our Sponsors
##### What's Changed * fix: sanitize dir names in the store by @​zkochan in https://github.com/pnpm/pnpm/pull/4726 * fix(create): pass all args to the executed create-app pkg by @​zkochan in https://github.com/pnpm/pnpm/pull/4730 * fix(git-resolver): resolve commits via https by @​zkochan in https://github.com/pnpm/pnpm/pull/4734 * refactor: setup by @​zkochan in https://github.com/pnpm/pnpm/pull/4731 * fix(config): checking global-bin-dir in PATH by @​zkochan in https://github.com/pnpm/pnpm/pull/4751

Full Changelog: pnpm/pnpm@v7.1.0...v7.1.1

postcss/postcss

v8.4.14

Compare Source

  • Print “old plugin API” warning only if plugin was used (by @​zardoy).
Microsoft/TypeScript

v4.7.2

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

vitest-dev/vitest

v0.13.1

Compare Source

Bug Fixes
Features

v0.13.0

Compare Source

Features

v0.12.10

Compare Source

Bug Fixes
Features

v0.12.9

Compare Source

Bug Fixes

v0.12.8

Compare Source

Bug Fixes

v0.12.7

Compare Source

Configuration

📅 Schedule: 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, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title chore(deps): update all non-major dependencies to ^5.24.0 chore(deps): update all non-major dependencies to ^5.25.0 May 17, 2022
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from e6b7b15 to bd2b859 Compare May 17, 2022 16:37
@renovate renovate bot changed the title chore(deps): update all non-major dependencies to ^5.25.0 chore(deps): update all non-major dependencies May 17, 2022
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 12 times, most recently from b094954 to 20a296c Compare May 24, 2022 19:19
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from 8f13ba7 to 0bf3723 Compare May 31, 2022 15:34
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0bf3723 to c472987 Compare June 1, 2022 06:38
@danielroe danielroe merged commit e7d74a7 into main Jun 1, 2022
@danielroe danielroe deleted the renovate/all-minor-patch branch June 1, 2022 07:26
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.

None yet
2 participants
@danielroe @renovate-bot