Update all non-major dependencies #664

renovate · 2023-02-08T03:56:11Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sentry/node (source)	`7.36.0` -> `7.38.0`
esbuild	`0.17.6` -> `0.17.10`
fastify (source)	`4.12.0` -> `4.13.0`
node-fetch	`1.0.1` -> `1.0.2`
pino (source)	`8.9.0` -> `8.11.0`
pino-pretty	`9.1.1` -> `9.3.0`
pnpm (source)	`7.26.3` -> `7.27.1`
prettier (source)	`2.8.3` -> `2.8.4`
remeda	`1.6.1` -> `1.6.2`
type-fest	`3.5.6` -> `3.6.0`
zod (source)	`3.20.2` -> `3.20.6`

Release Notes

getsentry/sentry-javascript

`v7.38.0`

Compare Source

feat: Put abs_path into stack frame object (#7167)
feat(integrations): Deprecate Offline integration (#7063)
feat(otel): Convert exception otel events to sentry errors (#7165)
feat(replay): Change LCP calculation (#7187)
feat(tracing): Support Apollo/GraphQL with NestJS (#7194)
feat(tracing): Track PerformanceResourceTiming.renderBlockingStatus (#7127)
feat(tracing|core): Remove transaction name change recording (#7197)
fix(browser): Ensure dedupe integration ignores non-errors (#7172)
fix(core): Skip empty integrations (#7204)
fix(nextjs): Fix faulty import in Next.js .d.ts (#7175)
fix(otel): Make otel.kind be a string (#7182)
fix(react): Make fallback render types more accurate (#7198)
fix(replay): Debounced flushes not respecting maxWait (#7207, #7208)
ref(replay): Improve logging for stopped replay (#7174)

Work in this release contributed by @lucas-zimermann. Thank you for your contribution!

Bundle size 📦

Path	Size
@sentry/browser - ES5 CDN Bundle (gzipped + minified)	20.05 KB
@sentry/browser - ES5 CDN Bundle (minified)	62.14 KB
@sentry/browser - ES6 CDN Bundle (gzipped + minified)	18.68 KB
@sentry/browser - ES6 CDN Bundle (minified)	55.29 KB
@sentry/browser - Webpack (gzipped + minified)	20.41 KB
@sentry/browser - Webpack (minified)	66.73 KB
@sentry/react - Webpack (gzipped + minified)	20.44 KB
@sentry/nextjs Client - Webpack (gzipped + minified)	47.78 KB
@sentry/browser + @sentry/tracing - ES5 CDN Bundle (gzipped + minified)	26.93 KB
@sentry/browser + @sentry/tracing - ES6 CDN Bundle (gzipped + minified)	25.2 KB
@sentry/replay ES6 CDN Bundle (gzipped + minified)	42.57 KB
@sentry/replay - Webpack (gzipped + minified)	36.78 KB
@sentry/browser + @sentry/tracing + @sentry/replay - ES6 CDN Bundle (gzipped + minified)	60.2 KB
@sentry/browser + @sentry/replay - ES6 CDN Bundle (gzipped + minified)	53.8 KB

`v7.37.2`

Compare Source

This release includes changes and fixes around text masking and blocking in Replay's rrweb dependency. See versions 1.102.0 and 1.103.0.

feat: Check blockSelector for blocking elements as well
feat: With maskAllText, mask the attributes: placeholder, title, aria-label
feat: fix masking on textarea
feat: Add maskAllText option

SDK Changes:

fix(replay): Fix svgs not getting unblocked (#7132)

`v7.37.1`

Compare Source

fix(browser): Support async in stack frame urls (#7131)
fix(nextjs): Make api route identifier stricter (#7126)
fix(node): Don't rely on this in http integration (#7135)
fix(replay): Fix missing fetch/xhr requests (#7134)
fix(tracing): Export defaultStackParser from tracing CDN bundles (#7116)

`v7.37.0`

Compare Source

feat: Add source map debug ids (#7068)
feat(browser): Add IndexedDb offline transport store (#6983)
feat(nextjs): Add auto-wrapping for server components (#6953)
feat(nextjs): Improve client stack traces (#7097)
feat(replay): Improve rrweb error ignoring (#7087 & #7094)
feat(replay): Send client_report when replay sending fails (#7093)
fix(node): LocalVariables, Improve frame matching for ESM (#7049)
fix(node): Add lru cache to http integration span map (#7064)
fix(replay): Export Replay from Sentry namespace in full CDN bundle (#7119)

Work in this release contributed by @JamesHenry. Thank you for your contribution!

evanw/esbuild

`v0.17.10`

Compare Source

Update esbuild's handling of CSS nesting to match the latest specification changes (#1945)

The syntax for the upcoming CSS nesting feature has recently changed. The @nest prefix that was previously required in some cases is now gone, and nested rules no longer have to start with & (as long as they don't start with an identifier or function token).

This release updates esbuild's pass-through handling of CSS nesting syntax to match the latest specification changes. So you can now use esbuild to bundle CSS containing nested rules and try them out in a browser that supports CSS nesting (which includes nightly builds of both Chrome and Safari).

However, I'm not implementing lowering of nested CSS to non-nested CSS for older browsers yet. While the syntax has been decided, the semantics are still in flux. In particular, there is still some debate about changing the fundamental way that CSS nesting works. For example, you might think that the following CSS is equivalent to a .outer .inner button { ... } rule:
```
.inner button {
  .outer & {
    color: red;
  }
}
```
But instead it's actually equivalent to a .outer :is(.inner button) { ... } rule which unintuitively also matches the following DOM structure:
```
<div class="inner">
  <div class="outer">
    <button></button>
  </div>
</div>
```
The :is() behavior is preferred by browser implementers because it's more memory-efficient, but the straightforward translation into a .outer .inner button { ... } rule is preferred by developers used to the existing CSS preprocessing ecosystem (e.g. SASS). It seems premature to commit esbuild to specific semantics for this syntax at this time given the ongoing debate.

Fix cross-file CSS rule deduplication involving url() tokens (#2936)

Previously cross-file CSS rule deduplication didn't handle url() tokens correctly. These tokens contain references to import paths which may be internal (i.e. in the bundle) or external (i.e. not in the bundle). When comparing two url() tokens for equality, the underlying import paths should be compared instead of their references. This release of esbuild fixes url() token comparisons. One side effect is that @font-face rules should now be deduplicated correctly across files:

/* Original code */
@&#8203;import "data:text/css, \
  @&#8203;import 'http://example.com/style.css'; \
  @&#8203;font-face { src: url(http://example.com/font.ttf) }";
@&#8203;import "data:text/css, \
  @&#8203;font-face { src: url(http://example.com/font.ttf) }";

/* Old output (with --bundle --minify) */
@&#8203;import"http://example.com/style.css";@&#8203;font-face{src:url(http://example.com/font.ttf)}@&#8203;font-face{src:url(http://example.com/font.ttf)}

/* New output (with --bundle --minify) */
@&#8203;import"http://example.com/style.css";@&#8203;font-face{src:url(http://example.com/font.ttf)}

`v0.17.9`

Compare Source

Parse rest bindings in TypeScript types (#2937)

Previously esbuild was unable to parse the following valid TypeScript code:
```
let tuple: (...[e1, e2, ...es]: any) => any
```
This release includes support for parsing code like this.

Fix TypeScript code translation for certain computed declare class fields (#2914)

In TypeScript, the key of a computed declare class field should only be preserved if there are no decorators for that field. Previously esbuild always preserved the key, but esbuild will now remove the key to match the output of the TypeScript compiler:

// Original code
declare function dec(a: any, b: any): any
declare const removeMe: unique symbol
declare const keepMe: unique symbol
class X {
    declare [removeMe]: any
    @&#8203;dec declare [keepMe]: any
}

// Old output
var _a;
class X {
}
removeMe, _a = keepMe;
__decorateClass([
  dec
], X.prototype, _a, 2);

// New output
var _a;
class X {
}
_a = keepMe;
__decorateClass([
  dec
], X.prototype, _a, 2);

Fix a crash with path resolution error generation (#2913)

In certain situations, a module containing an invalid import path could previously cause esbuild to crash when it attempts to generate a more helpful error message. This crash has been fixed.

`v0.17.8`

Compare Source

Fix a minification bug with non-ASCII identifiers (#2910)

This release fixes a bug with esbuild where non-ASCII identifiers followed by a keyword were incorrectly not separated by a space. This bug affected both the in and instanceof keywords. Here's an example of the fix:
```
// Original code
π in a

// Old output (with --minify --charset=utf8)
πin a;

// New output (with --minify --charset=utf8)
π in a;
```
Fix a regression with esbuild's WebAssembly API in version 0.17.6 (#2911)

Version 0.17.6 of esbuild updated the Go toolchain to version 1.20.0. This had the unfortunate side effect of increasing the amount of stack space that esbuild uses (presumably due to some changes to Go's WebAssembly implementation) which could cause esbuild's WebAssembly-based API to crash with a stack overflow in cases where it previously didn't crash. One such case is the package grapheme-splitter which contains code that looks like this:
```
if (
  (0x0300 <= code && code <= 0x036F) ||
  (0x0483 <= code && code <= 0x0487) ||
  (0x0488 <= code && code <= 0x0489) ||
  (0x0591 <= code && code <= 0x05BD) ||
  // ... many hundreds of lines later ...
) {
  return;
}
```
This edge case involves a chain of binary operators that results in an AST over 400 nodes deep. Normally this wouldn't be a problem because Go has growable call stacks, so the call stack would just grow to be as large as needed. However, WebAssembly byte code deliberately doesn't expose the ability to manipulate the stack pointer, so Go's WebAssembly translation is forced to use the fixed-size WebAssembly call stack. So esbuild's WebAssembly implementation is vulnerable to stack overflow in cases like these.

It's not unreasonable for this to cause a stack overflow, and for esbuild's answer to this problem to be "don't write code like this." That's how many other AST-manipulation tools handle this problem. However, it's possible to implement AST traversal using iteration instead of recursion to work around limited call stack space. This version of esbuild implements this code transformation for esbuild's JavaScript parser and printer, so esbuild's WebAssembly implementation is now able to process the grapheme-splitter package (at least when compiled with Go 1.20.0 and run with node's WebAssembly implementation).

`v0.17.7`

Compare Source

Change esbuild's parsing of TypeScript instantiation expressions to match TypeScript 4.8+ (#2907)

This release updates esbuild's implementation of instantiation expression erasure to match microsoft/TypeScript#49353. The new rules are as follows (copied from TypeScript's PR description):
When a potential type argument list is followed by
- a line break,
- an ( token,
- a template literal string, or
- any token except < or > that isn't the start of an expression,
we consider that construct to be a type argument list. Otherwise we consider the construct to be a < relational expression followed by a > relational expression.
Ignore sideEffects: false for imported CSS files (#1370, #1458, #2905)

This release ignores the sideEffects annotation in package.json for CSS files that are imported into JS files using esbuild's css loader. This means that these CSS files are no longer be tree-shaken.

Importing CSS into JS causes esbuild to automatically create a CSS entry point next to the JS entry point containing the bundled CSS. Previously packages that specified some form of "sideEffects": false could potentially cause esbuild to consider one or more of the JS files on the import path to the CSS file to be side-effect free, which would result in esbuild removing that CSS file from the bundle. This was problematic because the removal of that CSS is outwardly observable, since all CSS is global, so it was incorrect for previous versions of esbuild to tree-shake CSS files imported into JS files.

Add constant folding for certain additional equality cases (#2394, #2895)

This release adds constant folding for expressions similar to the following:

// Original input
console.log(
  null === 'foo',
  null === undefined,
  null == undefined,
  false === 0,
  false == 0,
  1 === true,
  1 == true,
)

// Old output
console.log(
  null === "foo",
  null === void 0,
  null == void 0,
  false === 0,
  false == 0,
  1 === true,
  1 == true
);

// New output
console.log(
  false,
  false,
  true,
  false,
  true,
  false,
  true
);

fastify/fastify

unjs/node-fetch-native

`v1.0.2`

Compare Source

🏡 Chore

release: 1.0.1 (abdb2ad)
release: 1.0.1 (7eb7dfd)
Update repo (d63453e)

❤️ Contributors

Pooya Parsa pooya@pi0.io

1.0.1 (2022-11-14)

pinojs/pino

`v8.11.0`

Compare Source

What's Changed

Add script to bump version by @jsumners in https://github.com/pinojs/pino/pull/1643
Add Node 19 to the CI by @mcollina in https://github.com/pinojs/pino/pull/1646
fix(docs): update multistream example and description by @Cheprer in https://github.com/pinojs/pino/pull/1649
fix msg precendence when sending a merging object with msg and err by @leon-volq in https://github.com/pinojs/pino/pull/1654

New Contributors

@Cheprer made their first contribution in https://github.com/pinojs/pino/pull/1649
@leon-volq made their first contribution in https://github.com/pinojs/pino/pull/1654

Full Changelog: pinojs/pino@v8.10.0...v8.11.0

`v8.10.0`

Compare Source

What's Changed

feat: add dedupe option to transport by @nekosaur in https://github.com/pinojs/pino/pull/1640

New Contributors

@nekosaur made their first contribution in https://github.com/pinojs/pino/pull/1640

Full Changelog: pinojs/pino@v8.9.0...v8.10.0

pinojs/pino-pretty

`v9.3.0`

Compare Source

What's Changed

feat: dont print escape backslash on strings containing escaped backslashes by @ademarsj in https://github.com/pinojs/pino-pretty/pull/401

Full Changelog: pinojs/pino-pretty@v9.2.0...v9.3.0

`v9.2.0`

Compare Source

What's Changed

update readme by @baterson in https://github.com/pinojs/pino-pretty/pull/381
Bump actions/dependency-review-action from 2 to 3 by @dependabot in https://github.com/pinojs/pino-pretty/pull/385
Bump tsd from 0.24.1 to 0.25.0 by @dependabot in https://github.com/pinojs/pino-pretty/pull/386
feat: adding possibility to pass an object as parameter to customLevels by @ademarsj in https://github.com/pinojs/pino-pretty/pull/400

New Contributors

@ademarsj made their first contribution in https://github.com/pinojs/pino-pretty/pull/400

Full Changelog: pinojs/pino-pretty@v9.1.1...v9.2.0

pnpm/pnpm

`v7.27.1`

Compare Source

Patch Changes

Add store path description to the pnpm cli help.
Print a hint that suggests to run pnpm store prune, when a tarball integrity error happens.
Don't retry installation if the integrity checksum of a package failed and no lockfile was present.
Fail with a meaningful error message when cannot parse a proxy URL.
The strict-ssl, ca, key, and cert settings should work with HTTPS proxy servers #4689.

Our Gold Sponsors

Our Silver Sponsors

`v7.27.0`

Compare Source

Minor Changes

A new resolution-mode added: lowest-direct. With this resolution mode direct dependencies will be resolved to their lowest versions. So if there is foo@^1.1.0 in the dependencies, then 1.1.0 will be installed, even if the latest version of foo is 1.2.0.
Support script selector with RegExp such as pnpm run /build:.*/ and execute the matched scripts with the RegExp #5871.

Patch Changes

Fix version number replacing for namespaced workspace packages. workspace:@foo/bar@* should be replaced with npm:@foo/bar@<version> on publish #6052.
When resolving dependencies, prefer versions that are already used in the root of the project. This is important to minimize the number of packages that will be nested during hoisting #6054.
Deduplicate direct dependencies.

Let's say there are two projects in the workspace that dependend on foo. One project has foo@1.0.0 in the dependencies while another one has foo@^1.0.0 in the dependencies. In this case, foo@1.0.0 should be installed to both projects as satisfies the version specs of both projects.
Use Map rather than Object in createPackageExtender to prevent read the prototype property to native function

Our Gold Sponsors

Our Silver Sponsors

prettier/prettier

`v2.8.4`

Compare Source

diff

Fix leading comments in mapped types with `readonly` (#13427 by @thorn0, @sosukesuzuki)

// Input
type Type = {
  // comment
  readonly [key in Foo];
};

// Prettier 2.8.3
type Type = {
  readonly // comment
  [key in Foo];
};

// Prettier 2.8.4
type Type = {
  // comment
  readonly [key in Foo];
};

Group params in opening block statements (#14067 by @jamescdavis)

This is a follow-up to #13930 to establish wrapping consistency between opening block statements and else blocks by
grouping params in opening blocks. This causes params to break to a new line together and not be split across lines
unless the length of params exceeds the print width. This also updates the else block wrapping to behave exactly the
same as opening blocks.

{{! Input }}
{{#block param param param param param param param param param param as |blockParam|}}
  Hello
{{else block param param param param param param param param param param as |blockParam|}}
  There
{{/block}}

{{! Prettier 2.8.3 }}
{{#block
  param
  param
  param
  param
  param
  param
  param
  param
  param
  param
  as |blockParam|
}}
  Hello
{{else block param
param
param
param
param
param
param
param
param
param}}
  There
{{/block}}

{{! Prettier 2.8.4 }}
{{#block
  param param param param param param param param param param
  as |blockParam|
}}
  Hello
{{else block
  param param param param param param param param param param
  as |blockParam|
}}
  There
{{/block}}

Ignore files in `.sl/` (#14206 by @bolinfest)

In Sapling SCM, .sl/ is the folder where it stores its state, analogous to .git/ in Git. It should be ignored in Prettier like the other SCM folders.

Recognize `@satisfies` in Closure-style type casts (#14262 by @fisker)

// Input
const a = /** @&#8203;satisfies {Record<string, string>} */ ({hello: 1337});
const b = /** @&#8203;type {Record<string, string>} */ ({hello: 1337});

// Prettier 2.8.3
const a = /** @&#8203;satisfies {Record<string, string>} */ { hello: 1337 };
const b = /** @&#8203;type {Record<string, string>} */ ({ hello: 1337 });

// Prettier 2.8.4
const a = /** @&#8203;satisfies {Record<string, string>} */ ({hello: 1337});
const b = /** @&#8203;type {Record<string, string>} */ ({hello: 1337});

Fix parens in inferred function return types with `extends` (#14279 by @fisker)

// Input
type Foo<T> = T extends ((a) => a is infer R extends string) ? R : never;

// Prettier 2.8.3 (First format)
type Foo<T> = T extends (a) => a is infer R extends string ? R : never;

// Prettier 2.8.3 (Second format)
SyntaxError: '?' expected. 

// Prettier 2.8.4
type Foo<T> = T extends ((a) => a is infer R extends string) ? R : never;