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

renovate · 2022-08-22T02:58:21Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sveltejs/adapter-auto (source)	`^1.0.0-next.64` -> `^1.0.0-next.65`
@sveltejs/kit (source)	`^1.0.0-next.415` -> `^1.0.0-next.428`
@typescript-eslint/eslint-plugin	`^5.33.0` -> `^5.33.1`
@typescript-eslint/parser	`^5.33.0` -> `^5.33.1`
carbon-components-svelte	`^0.68.0` -> `^0.70.0`
esbuild	`^0.15.3` -> `^0.15.5`
pnpm (source)	`7.9.0` -> `7.9.3`
pnpm (source)	`^7.9.0` -> `^7.9.3`
rollup (source)	`^2.78.0` -> `^2.78.1`
sass	`^1.54.4` -> `^1.54.5`
svelte-check	`^2.8.0` -> `^2.8.1`
vite	`^3.0.8` -> `^3.0.9`
vitest	`^0.22.0` -> `^0.22.1`

Release Notes

sveltejs/kit (@sveltejs/adapter-auto)

`v1.0.0-next.65`

Compare Source

Patch Changes

Updated dependencies [4bd84b32]:
- @sveltejs/adapter-vercel @1.0.0-next.67
- @sveltejs/adapter-netlify @1.0.0-next.71

sveltejs/kit (@sveltejs/kit)

`v1.0.0-next.428`

Compare Source

Patch Changes

Allow $app/stores to be used from anywhere on the browser (#6100)

use enumerable: false on "[x] no longer exists" getters so that they are not triggered by spreading (#6105)

Fix pattern matching for routes starting with an encoded @ symbol (#6110)

Fix typos in generating LayoutServerLoad.{name} type (#6123)

Fix sorting of files into +layout, +error, everything else. (#6108)

Add test folder to generated tsconfig (#6085)

`v1.0.0-next.427`

Compare Source

Patch Changes

Throw error if browser.hydrate is false and browser.router is true (#6086)

`v1.0.0-next.426`

Compare Source

Patch Changes

Avoid using [].at(-1) in the client (#6082)

`v1.0.0-next.425`

Compare Source

Patch Changes

Silence more unknown prop warnings coming from SvelteKit (#6078)

`v1.0.0-next.424`

Compare Source

Patch Changes

prevent duplicate module ids by disabling optimizeDeps for @sveltejs/kit (#6057)

Generate types when Svelte file missing, fix layout params (#6066)

Silence unknown prop warnings coming from SvelteKit (#6071)

`v1.0.0-next.423`

Compare Source

Patch Changes

Accumulate data from parent layouts into export let data (#6050)

`v1.0.0-next.422`

Compare Source

Patch Changes

[breaking] remove ability for +page.server.js to respond to GET requests with JSON (#6007)

Handle throw error/redirect in +server.js (#6028)

handle set-cookie in setHeaders (#6033)

Handle windows paths and regexp chars in kit.alias (#6034)

Make errors type in Action type less restrictive (#6022)

Check that data is serializable (#5987)

Fix parent data type for layouts referencing named layouts in the same folder (#6025)

`v1.0.0-next.421`

Compare Source

Patch Changes

Respect export const prerender = false in +page.server.js (#6012)

`v1.0.0-next.420`

Compare Source

Patch Changes

[fix] support linked @sveltejs/kit project in Vite 3.0.3+ (#5861)

`v1.0.0-next.419`

Compare Source

Patch Changes

Return a 303 response when a POST handler provides a location (#5989)

Generate __data.json files for server-side redirects when prerendering (#5997)

[chore] remove chokidar as dependency of kit (#5996)

Use relative asset paths where possible (#4250)

`v1.0.0-next.418`

Compare Source

Patch Changes

Prevent double import of env modules (#5955)

Tighten up params typings, fix load function typings, add event typings to generated types (#5974)

`v1.0.0-next.417`

Compare Source

Patch Changes

Render pages without a .svelte file in their proper layout/error files (#5972)

`v1.0.0-next.416`

Compare Source

Patch Changes

[fix] allow additional keys in svelte.config.js (#5961)

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

`v5.33.1`

Compare Source

Bug Fixes

missing placeholders in violation messages for no-unnecessary-type-constraint and no-unsafe-argument (and enable eslint-plugin/recommended rules internally) (#5453) (d023910)

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

`v5.33.1`

Compare Source

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

carbon-design-system/carbon-components-svelte

`v0.70.0`

Compare Source

Features

add filteredRowIds prop to ToolbarSearch to support pagination

`v0.69.0`

Compare Source

Features

dispatch on:click:header--select event in DataTable
dispatch on:click:row--select event in DataTable

evanw/esbuild

`v0.15.5`

Compare Source

Fix issues with Yarn PnP and Yarn's workspaces feature (#2476)

This release makes sure esbuild works with a Yarn feature called workspaces. Previously esbuild wasn't tested in this scenario, but this scenario now has test coverage. Getting this to work involved further tweaks to esbuild's custom code for what happens after Yarn PnP's path resolution algorithm runs, which is not currently covered by Yarn's PnP specification. These tweaks also fix exports map resolution with Yarn PnP for non-empty subpaths, which wasn't previously working.

`v0.15.4`

Compare Source

Consider TypeScript import assignments to be side-effect free (#2468)

TypeScript has a legacy import syntax for working with TypeScript namespaces that looks like this:
```
import { someNamespace } from './some-file'
import bar = someNamespace.foo;

// some-file.ts
export namespace someNamespace {
  export let foo = 123
}
```
Since esbuild converts TypeScript into JavaScript one file at a time, it doesn't know if bar is supposed to be a value or a type (or both, which TypeScript actually allows in this case). This is problematic because values are supposed to be kept during the conversion but types are supposed to be removed during the conversion. Currently esbuild keeps bar in the output, which is done because someNamespace.foo is a property access and property accesses run code that could potentially have a side effect (although there is no side effect in this case).

With this release, esbuild will now consider someNamespace.foo to have no side effects. This means bar will now be removed when bundling and when tree shaking is enabled. Note that it will still not be removed when tree shaking is disabled. This is because in this mode, esbuild supports adding additional code to the end of the generated output that's in the same scope as the module. That code could potentially make use of bar, so it would be incorrect to remove it. If you want bar to be removed, you'll have to enable tree shaking (which tells esbuild that nothing else depends on the unexported top-level symbols in the generated output).
Change the order of the banner and the "use strict" directive (#2467)

Previously the top of the file contained the following things in order:
1. The hashbang comment (see below) from the source code, if present
2. The "use strict" directive from the source code, if present
3. The content of esbuild's banner API option, if specified
This was problematic for people that used the banner API option to insert the hashbang comment instead of using esbuild's hashbang comment preservation feature. So with this release, the order has now been changed to:
1. The hashbang comment (see below) from the source code, if present
2. The content of esbuild's banner API option, if specified
3. The "use strict" directive from the source code, if present
I'm considering this change to be a bug fix instead of a breaking change because esbuild's documentation states that the banner API option can be used to "insert an arbitrary string at the beginning of generated JavaScript files". While this isn't technically true because esbuild may still insert the original hashbang comment before the banner, it's at least more correct now because the banner will now come before the "use strict" directive.

For context: JavaScript files recently allowed using a hashbang comment, which starts with #! and which must start at the very first character of the file. It allows Unix systems to execute the file directly as a script without needing to prefix it by the node command. This comment typically has the value #!/usr/bin/env node. Hashbang comments will be a part of ES2023 when it's released next year.
Fix exports maps with Yarn PnP path resolution (#2473)

The Yarn PnP specification says that to resolve a package path, you first resolve it to the absolute path of a directory, and then you run node's module resolution algorithm on it. Previously esbuild followed this part of the specification. However, doing this means that exports in package.json is not respected because node's module resolution algorithm doesn't interpret exports for absolute paths. So with this release, esbuild will now use a modified algorithm that deviates from both specifications but that should hopefully behave more similar to what Yarn actually does: node's module resolution algorithm is run with the original import path but starting from the directory returned by Yarn PnP.

pnpm/pnpm

`v7.9.3`

Compare Source

Patch Changes

Remove legacy signal handlers #5224

Our Gold Sponsors

##### Our Silver Sponsors

##### What's Changed * fix: remove legacy signal handlers by @d3lm in https://github.com/pnpm/pnpm/pull/5224

Full Changelog: pnpm/pnpm@v7.9.2...v7.9.3

`v7.9.2`

Compare Source

Patch Changes

When the same package is both in "peerDependencies" and in "dependencies", treat this dependency as a peer dependency if it may be resolved from the dependencies of parent packages #5210.
Update node-gyp to v9.
Update the compatibility database.

Our Gold Sponsors

##### Our Silver Sponsors

`v7.9.1`

Compare Source

Patch Changes

pnpm setup: don't use setx to set env variables on Windows.

Our Gold Sponsors

#### Our Silver Sponsors

rollup/rollup

`v2.78.1`

Compare Source

2022-08-19

Bug Fixes

Avoid inferring "arguments" as name for a default export placeholder variable (#4613)

Pull Requests

#4613: Prevent using arguments for generated variable names (@lukastaegert)

sass/dart-sass

`v1.54.5`

Compare Source

Properly consider a ~ c to be a superselector of a ~ b ~ c and a + b + c.
Properly consider b > c to be a superselector of a > b > c, and similarly
for other combinators.
Properly calculate specificity for selector pseudoclasses.
Deprecate use of random() when $limit has units to make it explicit that
random() currently ignores units. A future version will no longer ignore
units.
Don't throw an error when the same module is @forwarded multiple times
through a configured module.

Embedded Sass

Rather than downloading the embedded compiler for the local platform on
install, the sass-embedded npm package now declares optional dependencies on
platform-specific embedded compiler packages.

sveltejs/language-tools

`v2.8.1`

Compare Source

(fix) allow SapperAnchorProps & SvelteKitAnchorProps on svelte:element (#1577)

vitejs/vite

`v3.0.9`

Compare Source

feat(ssr): warn if cant analyze dynamic import (#9738) (e0ecb80), closes #9738
fix: dynamic import path contain ../ and its own directory (#9350) (c6870f3), closes #9350
fix: legacy no resolve asset urls (#9507) (1d6a1eb), closes #9507
fix: print error file path when using rollupOptions.output.dir (fix #9100) (#9111) (3bffd14), closes #9100 #9111
fix: skip undefined proxy entry (#9622) (e396d67), closes #9622
fix(hmr): duplicate link tags (#9697) (9aa9515), closes #9697
fix(import-analysis): escape quotes (#9729) (21515f1), closes #9729
docs: fix typos in comments and documentation (#9711) (0571232), closes #9711
docs: update import.meta.glob jsdocs (#9709) (15ff3a2), closes #9709
chore(deps): update all non-major dependencies (#9675) (4e56e87), closes #9675
chore(deps): update dependency es-module-lexer to v1 (#9576) (1d8613f), closes #9576
perf: avoid ssrTransform object allocation (#9706) (6e58d9d), closes #9706

vitest-dev/vitest

`v0.22.1`

Compare Source

🚀 Features

Restart vitest on config change - by @antfu (c663f)
Show transform time - by @antfu (b54a1)
vite-node: moduleCache.invalidateDepTree utiltity - by @antfu in https://github.com/vitest-dev/vitest/issues/1872

🐞 Bug Fixes

Convert string coverage reporters to array - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/1860
Explicitly import performance - by @antfu (870d1)

View changes on GitHub

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

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

chore(deps): update all non-major dependencies

8fa9634

renovate bot added the dependencies label Aug 22, 2022

dominikg approved these changes Aug 22, 2022

View reviewed changes

dominikg merged commit 1ed3df1 into main Aug 22, 2022

dominikg deleted the renovate/all-minor-patch branch August 22, 2022 10:45

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

renovate bot commented Aug 22, 2022

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

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

Conversation

renovate bot commented Aug 22, 2022

Release Notes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Bug Fixes

Patch Changes

Our Gold Sponsors

Patch Changes

Our Gold Sponsors

Patch Changes

Our Gold Sponsors

Bug Fixes

Pull Requests

Embedded Sass

🚀 Features

🐞 Bug Fixes

Configuration