Skip to content

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

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
Merged
merged 2 commits into from
Feb 4, 2023
Merged

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

merged 2 commits into from
Feb 4, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 30, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@sveltejs/adapter-node (source) ^1.1.4 -> ^1.1.6 age adoption passing confidence
@sveltejs/kit (source) ^1.2.6 -> ^1.3.10 age adoption passing confidence
@typescript-eslint/eslint-plugin ^5.49.0 -> ^5.50.0 age adoption passing confidence
@typescript-eslint/parser ^5.49.0 -> ^5.50.0 age adoption passing confidence
carbon-components-svelte ^0.72.0 -> ^0.72.1 age adoption passing confidence
deepmerge ^4.2.2 -> ^4.3.0 age adoption passing confidence
esbuild ^0.17.4 -> ^0.17.5 age adoption passing confidence
eslint (source) ^8.32.0 -> ^8.33.0 age adoption passing confidence
playwright-core (source) ^1.29.2 -> ^1.30.0 age adoption passing confidence
pnpm (source) 7.25.1 -> 7.26.3 age adoption passing confidence
sass ^1.57.1 -> ^1.58.0 age adoption passing confidence
svelte-check ^3.0.2 -> ^3.0.3 age adoption passing confidence
typescript (source) ^4.9.4 -> ^4.9.5 age adoption passing confidence
vite (source) ^4.0.4 -> ^4.1.1 age adoption passing confidence
vitest ^0.28.1 -> ^0.28.4 age adoption passing confidence

Release Notes

sveltejs/kit (@​sveltejs/adapter-node)

v1.1.6

Compare Source

Patch Changes
  • fix: correctly redirect trailing slashes for adapter-node (#​8857)

v1.1.5

Compare Source

Patch Changes
sveltejs/kit (@​sveltejs/kit)

v1.3.10

Compare Source

Patch Changes
  • fix: preserve build error messages (#​8846)

v1.3.9

Compare Source

Patch Changes
  • fix: output errors properly if pages fail to compile (#​8813)

v1.3.8

Compare Source

Patch Changes
  • fix: remove Vite manifest before running adapter (#​8815)

v1.3.7

Compare Source

Patch Changes

  • fix: only show prerendering message when actually prerendering (#​8809)

  • fix: handle anchors with special chars when navigating (#​8806)

  • fix: await finalise hook and run it only once (#​8817)

v1.3.6

Compare Source

Patch Changes

  • fix: allow rest parameters to follow multiple optional - or not - parameters (#​8761)

  • fix: consider headers when constructing request hash (#​8754)

v1.3.5

Compare Source

Patch Changes

  • docs: fix typo (#​8790)

  • fix: build error on layout with missing leaves (#​8792)

  • fix: handle hash links with non-ASCII characters when navigating (#​8767)

v1.3.4

Compare Source

Patch Changes

v1.3.3

Compare Source

Patch Changes
  • fix: forward process.env to child process (#​8777)

v1.3.2

Compare Source

Patch Changes
  • fix: take base path into account when preloading code (#​8748)

v1.3.1

Compare Source

Patch Changes
  • fix: preserve build error messages (#​8846)

v1.3.0

Compare Source

Minor Changes
  • feat: allow generated tsconfig to be modified (#​8606)
Patch Changes
  • fix: skip navigation hooks on popstate events when only hash changed (#​8730)

v1.2.10

Compare Source

Patch Changes

  • chore: restrict methods allowed for POST (#​8721)

  • fix: provide proper error when POSTing to a missing page endpoint (#​8714)

v1.2.9

Compare Source

Patch Changes
  • fix: reapply exports alignment after Vite dependency optimizations (#​8690)

v1.2.8

Compare Source

Patch Changes
  • fix: include base path in path to start script (#​8651)

v1.2.7

Compare Source

Patch Changes
  • fix: set headers when throwing redirect in handle (#​8648)
typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v5.50.0

Compare Source

Bug Fixes
  • eslint-plugin: [ban-ts-comment] counts graphemes instead of String.prototype.length (#​5704) (09d57ce)
  • eslint-plugin: [prefer-optional-chain] fix ThisExpression and PrivateIdentifier errors (#​6028) (85e783c)
  • eslint-plugin: [prefer-optional-chain] fixer produces wrong logic (#​5919) (b0f6c8e), closes #​1438
Features
  • eslint-plugin: add key-spacing rule extension for interface & type declarations (#​6211) (67706e7)
typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v5.50.0

Compare Source

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

carbon-design-system/carbon-components-svelte

v0.72.1

Compare Source

TehShrike/deepmerge

v4.3.0

Compare Source

  • Avoid thrown errors if the target doesn't have propertyIsEnumerable. #​252
evanw/esbuild

v0.17.5

Compare Source

  • Parse const type parameters from TypeScript 5.0

    The TypeScript 5.0 beta announcement adds const type parameters to the language. You can now add the const modifier on a type parameter of a function, method, or class like this:

    type HasNames = { names: readonly string[] };
const getNamesExactly = <const T extends HasNames>(arg: T): T["names"] => arg.names;
const names = getNamesExactly({ names: ["Alice", "Bob", "Eve"] });

    The type of names in the above example is readonly ["Alice", "Bob", "Eve"]. Marking the type parameter as const behaves as if you had written as const at every use instead. The above code is equivalent to the following TypeScript, which was the only option before TypeScript 5.0:

    type HasNames = { names: readonly string[] };
const getNamesExactly = <T extends HasNames>(arg: T): T["names"] => arg.names;
const names = getNamesExactly({ names: ["Alice", "Bob", "Eve"] } as const);

    You can read the announcement for more information.

  • Make parsing generic async arrow functions more strict in .tsx files

    Previously esbuild's TypeScript parser incorrectly accepted the following code as valid:

    let fn = async <T> () => {};

    The official TypeScript parser rejects this code because it thinks it's the identifier async followed by a JSX element starting with <T>. So with this release, esbuild will now reject this syntax in .tsx files too. You'll now have to add a comma after the type parameter to get generic arrow functions like this to parse in .tsx files:

    let fn = async <T,> () => {};

  • Allow the in and out type parameter modifiers on class expressions

    TypeScript 4.7 added the in and out modifiers on the type parameters of classes, interfaces, and type aliases. However, while TypeScript supported them on both class expressions and class statements, previously esbuild only supported them on class statements due to an oversight. This release now allows these modifiers on class expressions too:

    declare let Foo: any;
Foo = class <in T> { };
Foo = class <out T> { };

  • Update enum constant folding for TypeScript 5.0

    TypeScript 5.0 contains an updated definition of what it considers a constant expression:

    An expression is considered a constant expression if it is

    • a number or string literal,
    • a unary +, -, or ~ applied to a numeric constant expression,
    • a binary +, -, *, /, %, **, <<, >>, >>>, |, &, ^ applied to two numeric constant expressions,
    • a binary + applied to two constant expressions whereof at least one is a string,
    • a template expression where each substitution expression is a constant expression,
    • a parenthesized constant expression,
    • a dotted name (e.g. x.y.z) that references a const variable with a constant expression initializer and no type annotation,
    • a dotted name that references an enum member with an enum literal type, or
    • a dotted name indexed by a string literal (e.g. x.y["z"]) that references an enum member with an enum literal type.

    This impacts esbuild's implementation of TypeScript's const enum feature. With this release, esbuild will now attempt to follow these new rules. For example, you can now initialize an enum member with a template literal expression that contains a numeric constant:

    // Original input
const enum Example {
  COUNT = 100,
  ERROR = `Expected ${COUNT} items`,
}
console.log(
  Example.COUNT,
  Example.ERROR,
)

// Old output (with --tree-shaking=true)
var Example = /* @&#8203;__PURE__ */ ((Example2) => {
  Example2[Example2["COUNT"] = 100] = "COUNT";
  Example2[Example2["ERROR"] = `Expected ${100 /* COUNT */} items`] = "ERROR";
  return Example2;
})(Example || {});
console.log(
  100 /* COUNT */,
  Example.ERROR
);

// New output (with --tree-shaking=true)
console.log(
  100 /* COUNT */,
  "Expected 100 items" /* ERROR */
);

    These rules are not followed exactly due to esbuild's limitations. The rule about dotted references to const variables is not followed both because esbuild's enum processing is done in an isolated module setting and because doing so would potentially require esbuild to use a type system, which it doesn't have. For example:

    // The TypeScript compiler inlines this but esbuild doesn't:
declare const x = 'foo'
const enum Foo { X = x }
console.log(Foo.X)

    Also, the rule that requires converting numbers to a string currently only followed for 32-bit signed integers and non-finite numbers. This is done to avoid accidentally introducing a bug if esbuild's number-to-string operation doesn't exactly match the behavior of a real JavaScript VM. Currently esbuild's number-to-string constant folding is conservative for safety.

  • Forbid definite assignment assertion operators on class methods

    In TypeScript, class methods can use the ? optional property operator but not the ! definite assignment assertion operator (while class fields can use both):

    class Foo {
  // These are valid TypeScript
  a?
  b!
  x?() {}

  // This is invalid TypeScript
  y!() {}
}

    Previously esbuild incorrectly allowed the definite assignment assertion operator with class methods. This will no longer be allowed starting with this release.

eslint/eslint

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)
Microsoft/playwright

v1.30.0

Compare Source

🎉 Happy New Year 🎉

Maintenance release with bugfixes and new browsers only. We are baking some nice features for v1.31.

Browser Versions
  • Chromium 110.0.5481.38
  • Mozilla Firefox 108.0.2
  • WebKit 16.4

This version was also tested against the following stable channels:

  • Google Chrome 109
  • Microsoft Edge 109
pnpm/pnpm

v7.26.3

Compare Source

Patch Changes

  • Directories inside the virtual store should not contain the ( or ) chars. This is to fix issues with storybook and the new v6 pnpm-lock.yaml lockfile format #​5976.
  • The update command should not replace dependency versions specified via dist-tags #​5996.
  • Fixed an issue that was causing pnpm to stuck forever during installation #​5909.

Our Gold Sponsors

Our Silver Sponsors

v7.26.2

Compare Source

Patch Changes

  • Wrap text in pnpm audit output for better readability #​5981
  • Fix "cross-device link not permitted" error when node-linker is set to hoisted #​5992.

Our Gold Sponsors

Our Silver Sponsors

v7.26.1

Compare Source

Patch Changes

  • Fixed out of memory error that sometimes happens when node-linker is set to hoisted #​5988.
  • Fixed EMFILE: too many open files by using graceful-fs for reading bin files of dependencies #​5887.
  • Fix lockfile v6 on projects that use patched dependencies #​5967.

Our Gold Sponsors

Our Silver Sponsors

v7.26.0

Compare Source

Minor Changes

Patch Changes

  • Packages hoisted to the virtual store are not removed on repeat install, when the non-headless algorithm runs the installation #​5971.
  • prepublishOnly and prepublish should not be executed on pnpm pack #​2941.

Our Gold Sponsors

Our Silver Sponsors
sass/dart-sass

v1.58.0

Compare Source

  • Remove sourcemap comments from Sass sources. The generated sourcemap comment
    for the compiled CSS output remains unaffected.

  • Fix a bug in @extend logic where certain selectors with three or more
    combinators were incorrectly considered superselectors of similar selectors
    with fewer combinators, causing them to be incorrectly trimmed from the
    output.

  • Produce a better error message for a number with a leading + or -, a
    decimal point, but no digits.

  • Produce a better error message for a nested property whose name starts with
    --.

  • Fix a crash when a selector ends in an escaped backslash.

  • Add the relative length units from CSS Values 4 and CSS Contain 3 as known
    units to validate bad computation in calc.

Command Line Interface
  • The --watch flag will now track loads through calls to meta.load-css() as
    long as their URLs are literal strings without any interpolation.
sveltejs/language-tools

v3.0.3

Compare Source

  • (fix) make --no-tsconfig flag work (#​1843)
Microsoft/TypeScript

v4.9.5: TypeScript 4.9.5

Compare Source

For release notes, check out the release announcement.

Downloads are available on:

Changes:

vitejs/vite

v4.1.1

Compare Source

v4.1.0

Compare Source

Vite 4.1 updates to the latest versions of Rollup and esbuild. Check out the new Rollup docs, that are now powered by VitePress making the navigation between Vite and Rollup docs easier for users.

Vite docs got a theme update migrating to the latest version of VitePress.

As part of Vite 4, the Vue and React plugins have been extracted out of the monorepo. Although their release cycle will no longer follow Vite releases moving forward, Vite 4.1 is released in parallel with new versions of @​vitejs/plugin-react and @​vitejs/plugin-react-swc. @​vitejs/plugin-react 3.1.0 reworks the way HMR is handled fixing many edge cases and @​vitejs/plugin-react-swc 3.1.0 adds support for SWC plugins.

There is also a new major for @​vitejs/plugin-legacy, see changelog for v4.0.0. This version contains breaking changes:

Features
Bug Fixes

Configuration

📅 Schedule: Branch creation - "before 3am 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.

@changeset-bot
Copy link

changeset-bot bot commented Jan 30, 2023 •
edited
Loading

⚠️ No Changeset found

Latest commit: 250665f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 10 times, most recently from 250665f to e6cd893 Compare February 2, 2023 21:10
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from e6cd893 to 5f9f85f Compare February 3, 2023 12:35
@renovate
Copy link
Contributor Author

renovate bot commented Feb 3, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

@dominikg dominikg merged commit 9d99ff5 into main Feb 4, 2023
@dominikg dominikg deleted the renovate/all-minor-patch branch February 4, 2023 10:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@dominikg dominikg dominikg approved these changes

Assignees
No one assigned
Labels
dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@dominikg