Update all non-major dependencies #717

renovate · 2023-07-24T02:16:31Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sentry/node (source)	`7.59.3` -> `7.64.0`
better-sqlite3	`8.5.0` -> `8.5.1`
esbuild	`0.18.15` -> `0.19.2`
fastify (source)	`4.20.0` -> `4.21.0`
node-fetch	`1.2.0` -> `1.3.3`
pino (source)	`8.14.1` -> `8.15.0`
pino-pretty	`10.0.1` -> `10.2.0`
pnpm (source)	`8.6.9` -> `8.6.12`
prettier (source)	`3.0.0` -> `3.0.2`
remeda	`1.24.0` -> `1.25.2`
type-fest	`4.0.0` -> `4.2.0`
zod (source)	`3.21.4` -> `3.22.2`

Release Notes

getsentry/sentry-javascript (@sentry/node)

`v7.64.0`

Compare Source

feat(core): Add setMeasurement export (#8791)
fix(nextjs): Check for existence of default export when wrapping pages (#8794)
fix(nextjs): Ensure imports are valid relative paths (#8799)
fix(nextjs): Only re-export default export if it exists (#8800)

`v7.63.0`

Compare Source

build(deps): bump @opentelemetry/instrumentation from 0.41.0 to 0.41.2
feat(eventbuilder): Export exceptionFromError for use in hybrid SDKs (#8766)
feat(node-experimental): Re-export from node (#8786)
feat(tracing): Add db connection attributes for mysql spans (#8775)
feat(tracing): Add db connection attributes for postgres spans (#8778)
feat(tracing): Improve data collection for mongodb spans (#8774)
fix(nextjs): Execute sentry config independently of autoInstrumentServerFunctions and autoInstrumentAppDirectory (#8781)
fix(replay): Ensure we do not flush if flush took too long (#8784)
fix(replay): Ensure we do not try to flush when we force stop replay (#8783)
fix(replay): Fix hasCheckout handling (#8782)
fix(replay): Handle multiple clicks in a short time (#8773)
ref(replay): Skip events being added too long after initial segment (#8768)

`v7.62.0`

Compare Source

Important Changes

feat(integrations): Add ContextLines integration for html-embedded JS stack frames (#8699)

This release adds the ContextLines integration as an optional integration for the Browser SDKs to @sentry/integrations.

This integration adds source code from inline JavaScript of the current page's HTML (e.g. JS in <script> tags) to stack traces of captured errors.
It can't collect source code from assets referenced by your HTML (e.g. <script src="..." />).

The ContextLines integration is useful when you have inline JS code in HTML pages that can't be accessed by Sentry's backend, for example, due to a login-protected page.

import { ContextLines } from "@&#8203;sentry/integrations";

Sentry.init({
  // ...
  integrations: [
    new ContextLines({
      // The number of lines to collect before and after each stack frame's line number
      // Defaults to 7
      frameContextLines: 7,
    }),
  ],
});

Other Changes

fix(nextjs): Make all wrappers isomorphic and available in all runtimes (#8743)
fix(replay): Cancel debounce when replay is too short/long (#8742)
fix(utils): dirname and basename should handle Windows paths (#8737)
ref: Hoist flush, close, and lastEventId into @sentry/core (#8731)
ref(node): Don't call JSON.stringify on prisma client when logging (#8745)

`v7.61.1`

Compare Source

feat(nextjs): Add AsyncLocalStorage async context strategy to edge SDK (#8720)
fix(core): Filter internal API frames for synthetic frames (#8710)
fix(integrations): Capture exception if any arg to console method is an error (#8671)
fix(node-experimental): Update auto integration lookup & readme (#8690)
fix(node): Add availablility check on current hub to Node ContextLines integration (#8715)
fix(replay): Ensure buffer sessions end after capturing an error (#8713)
fix(replay): Ensure buffer->session switch is reliable (#8712)
fix(replay): Ensure we debounce flush if replay too short (#8716)
fix(replay): Improve capture of errorIds/traceIds (#8678)
fix(tracing): Set correct parent span id on fetch sentry-trace header (#8687)
fix(utils): Avoid pre_context and context_line overlap if frame lineno is out of bounds (#8722)
ref(replay): Improve status logging (#8709)
ref(nextjs): Allow withSentryConfig to accept async config function (#8721)

`v7.61.0`

Compare Source

Important Changes

feat(node-experimental): Add @sentry/node-experimental package as MVP for POTEL (#8609)

This introduces a new, experimental package, @sentry/node-experimental.
This is a variant of the Node SDK which uses OpenTelemetry under the hood for performance instrumentation.

Note that this package is very much WIP, considered unstable and may change at any time.
No SemVer guarantees apply whatsoever. Still, if you're brave enough you can give it a try.
Read more about @sentry/node-experimental

Other Changes

fix(node): Don't set extra baggage headers (#8657)
fix(tracing): Trim idle transaction spans if they exceed final timeout (#8653)

`v7.60.1`

Compare Source

fix(nextjs): Match folder paths with trailing separator (#8615)
fix(replay): Ignore clicks with shift pressed (#8648)
fix(replay): Use session.started for min/max duration check (#8617)

`v7.60.0`

Compare Source

Important Changes

feat(replay): Ensure min/max duration when flushing (#8596)

We will not send replays that are <5s long anymore. Additionally, we also added further safeguards to avoid overly long (>1h) replays.
You can optionally configure the min. replay duration (defaults to 5s):

new Replay({
  minReplayDuration: 10000 // in ms - note that this is capped at 15s max!
})

Other Changes

fix(profiling): Align to SDK selected time origin (#8599)
fix(replay): Ensure multi click has correct timestamps (#8591)
fix(utils): Truncate aggregate exception values (LinkedErrors) (#8593)

WiseLibs/better-sqlite3 (better-sqlite3)

`v8.5.1`

Compare Source

What's Changed

Add support for electron v26 prebuilds by @m4heshd in https://github.com/WiseLibs/better-sqlite3/pull/1042

Full Changelog: WiseLibs/better-sqlite3@v8.5.0...v8.5.1

evanw/esbuild (esbuild)

`v0.19.2`

Compare Source

Update how CSS nesting is parsed again

CSS nesting syntax has been changed again, and esbuild has been updated to match. Type selectors may now be used with CSS nesting:
```
.foo {
  div {
    color: red;
  }
}
```
Previously this was disallowed in the CSS specification because it's ambiguous whether an identifier is a declaration or a nested rule starting with a type selector without requiring unbounded lookahead in the parser. It has now been allowed because the CSS working group has decided that requiring unbounded lookahead is acceptable after all.

Note that this change means esbuild no longer considers any existing browser to support CSS nesting since none of the existing browsers support this new syntax. CSS nesting will now always be transformed when targeting a browser. This situation will change in the future as browsers add support for this new syntax.
Fix a scope-related bug with --drop-labels= (#3311)

The recently-released --drop-labels= feature previously had a bug where esbuild's internal scope stack wasn't being restored properly when a statement with a label was dropped. This could manifest as a tree-shaking issue, although it's possible that this could have also been causing other subtle problems too. The bug has been fixed in this release.
Make renamed CSS names unique across entry points (#3295)

Previously esbuild's generated names for local names in CSS were only unique within a given entry point (or across all entry points when code splitting was enabled). That meant that building multiple entry points with esbuild could result in local names being renamed to the same identifier even when those entry points were built simultaneously within a single esbuild API call. This problem was especially likely to happen with minification enabled. With this release, esbuild will now avoid renaming local names from two separate entry points to the same name if those entry points were built with a single esbuild API call, even when code splitting is disabled.
Fix CSS ordering bug with @layer before @import

CSS lets you put @layer rules before @import rules to define the order of layers in a stylesheet. Previously esbuild's CSS bundler incorrectly ordered these after the imported files because before the introduction of cascade layers to CSS, imported files could be bundled by removing the @import rules and then joining files together in the right order. But with @layer, CSS files may now need to be split apart into multiple pieces in the bundle. For example:
```
/* Original code */
@&#8203;layer start;
@&#8203;import "data:text/css,@&#8203;layer inner.start;";
@&#8203;import "data:text/css,@&#8203;layer inner.end;";
@&#8203;layer end;

/* Old output (with --bundle) */
@&#8203;layer inner.start;
@&#8203;layer inner.end;
@&#8203;layer start;
@&#8203;layer end;

/* New output (with --bundle) */
@&#8203;layer start;
@&#8203;layer inner.start;
@&#8203;layer inner.end;
@&#8203;layer end;
```

Unwrap nested duplicate @media rules (#3226)

With this release, esbuild's CSS minifier will now automatically unwrap duplicate nested @media rules:

/* Original code */
@&#8203;media (min-width: 1024px) {
  .foo { color: red }
  @&#8203;media (min-width: 1024px) {
    .bar { color: blue }
  }
}

/* Old output (with --minify) */
@&#8203;media (min-width: 1024px){.foo{color:red}@&#8203;media (min-width: 1024px){.bar{color:#&#8203;00f}}}

/* New output (with --minify) */
@&#8203;media (min-width: 1024px){.foo{color:red}.bar{color:#&#8203;00f}}

These rules are unlikely to be authored manually but may result from using frameworks such as Tailwind to generate CSS.

`v0.19.1`

Compare Source

Fix a regression with baseURL in tsconfig.json (#3307)

The previous release moved tsconfig.json path resolution before --packages=external checks to allow the paths field in tsconfig.json to avoid a package being marked as external. However, that reordering accidentally broke the behavior of the baseURL field from tsconfig.json. This release moves these path resolution rules around again in an attempt to allow both of these cases to work.
Parse TypeScript type arguments for JavaScript decorators (#3308)

When parsing JavaScript decorators in TypeScript (i.e. with experimentalDecorators disabled), esbuild previously didn't parse type arguments. Type arguments will now be parsed starting with this release. For example:
```
@&#8203;foo<number>
@&#8203;bar<number, string>()
class Foo {}
```
Fix glob patterns matching extra stuff at the end (#3306)

Previously glob patterns such as ./*.js would incorrectly behave like ./*.js* during path matching (also matching .js.map files, for example). This was never intentional behavior, and has now been fixed.
Change the permissions of esbuild's generated output files (#3285)

This release changes the permissions of the output files that esbuild generates to align with the default behavior of node's fs.writeFileSync function. Since most tools written in JavaScript use fs.writeFileSync, this should make esbuild more consistent with how other JavaScript build tools behave.

The full Unix-y details: Unix permissions use three-digit octal notation where the three digits mean "user, group, other" in that order. Within a digit, 4 means "read" and 2 means "write" and 1 means "execute". So 6 == 4 + 2 == read + write. Previously esbuild uses 0644 permissions (the leading 0 means octal notation) but the permissions for fs.writeFileSync defaults to 0666, so esbuild will now use 0666 permissions. This does not necessarily mean that the files esbuild generates will end up having 0666 permissions, however, as there is another Unix feature called "umask" where the operating system masks out some of these bits. If your umask is set to 0022 then the generated files will have 0644 permissions, and if your umask is set to 0002 then the generated files will have 0664 permissions.
Fix a subtle CSS ordering issue with @import and @layer

With this release, esbuild may now introduce additional @layer rules when bundling CSS to better preserve the layer ordering of the input code. Here's an example of an edge case where this matters:
```
/* entry.css */
@&#8203;import "a.css";
@&#8203;import "b.css";
@&#8203;import "a.css";
```
```
/* a.css */
@&#8203;layer a {
  body {
    background: red;
  }
}
```
```
/* b.css */
@&#8203;layer b {
  body {
    background: green;
  }
}
```
This CSS should set the body background to green, which is what happens in the browser. Previously esbuild generated the following output which incorrectly sets the body background to red:
```
/* b.css */
@&#8203;layer b {
  body {
    background: green;
  }
}

/* a.css */
@&#8203;layer a {
  body {
    background: red;
  }
}
```
This difference in behavior is because the browser evaluates a.css + b.css + a.css (in CSS, each @import is replaced with a copy of the imported file) while esbuild was only writing out b.css + a.css. The first copy of a.css wasn't being written out by esbuild for two reasons: 1) bundlers care about code size and try to avoid emitting duplicate CSS and 2) when there are multiple copies of a CSS file, normally only the last copy matters since the last declaration with equal specificity wins in CSS.

However, @layer was recently added to CSS and for @layer the first copy matters because layers are ordered using their first location in source code order. This introduction of @layer means esbuild needs to change its bundling algorithm. An easy solution would be for esbuild to write out a.css twice, but that would be inefficient. So what I'm going to try to have esbuild do with this release is to write out an abbreviated form of the first copy of a CSS file that only includes the @layer information, and then still only write out the full CSS file once for the last copy. So esbuild's output for this edge case now looks like this:
```
/* a.css */
@&#8203;layer a;

/* b.css */
@&#8203;layer b {
  body {
    background: green;
  }
}

/* a.css */
@&#8203;layer a {
  body {
    background: red;
  }
}
```
The behavior of the bundled CSS now matches the behavior of the unbundled CSS. You may be wondering why esbuild doesn't just write out a.css first followed by b.css. That would work in this case but it doesn't work in general because for any rules outside of a @layer rule, the last copy should still win instead of the first copy.
Fix a bug with esbuild's TypeScript type definitions (#3299)

This release fixes a copy/paste error with the TypeScript type definitions for esbuild's JS API:
```
 export interface TsconfigRaw {
   compilerOptions?: {
-    baseUrl?: boolean
+    baseUrl?: string
     ...
   }
 }
```
This fix was contributed by @privatenumber.

`v0.19.0`

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.18.0 or ~0.18.0. See npm's documentation about semver for more information.

Handle import paths containing wildcards (#56, #700, #875, #976, #2221, #2515)

This release introduces wildcards in import paths in two places:
- Entry points
  
  You can now pass a string containing glob-style wildcards such as ./src/*.ts as an entry point and esbuild will search the file system for files that match the pattern. This can be used to easily pass esbuild all files with a certain extension on the command line in a cross-platform way. Previously you had to rely on the shell to perform glob expansion, but that is obviously shell-dependent and didn't work at all on Windows. Note that to use this feature on the command line you will have to quote the pattern so it's passed verbatim to esbuild without any expansion by the shell. Here's an example:
```
esbuild --minify "./src/*.ts" --outdir=out
```
  Specifically the * character will match any character except for the / character, and the /**/ character sequence will match a path separator followed by zero or more path elements. Other wildcard operators found in glob patterns such as ? and [...] are not supported.
- Run-time import paths
  
  Import paths that are evaluated at run-time can now be bundled in certain limited situations. The import path expression must be a form of string concatenation and must start with either ./ or ../. Each non-string expression in the string concatenation chain becomes a wildcard. The * wildcard is chosen unless the previous character is a /, in which case the /**/* character sequence is used. Some examples:
```
// These two forms are equivalent
const json1 = await import('./data/' + kind + '.json')
const json2 = await import(`./data/${kind}.json`)
```
  This feature works with require(...) and import(...) because these can all accept run-time expressions. It does not work with import and export statements because these cannot accept run-time expressions. If you want to prevent esbuild from trying to bundle these imports, you should move the string concatenation expression outside of the require(...) or import(...). For example:
```
// This will be bundled
const json1 = await import('./data/' + kind + '.json')

// This will not be bundled
const path = './data/' + kind + '.json'
const json2 = await import(path)
```
  Note that using this feature means esbuild will potentially do a lot of file system I/O to find all possible files that might match the pattern. This is by design, and is not a bug. If this is a concern, I recommend either avoiding the /**/ pattern (e.g. by not putting a / before a wildcard) or using this feature only in directory subtrees which do not have many files that don't match the pattern (e.g. making a subdirectory for your JSON files and explicitly including that subdirectory in the pattern).
Path aliases in tsconfig.json no longer count as packages (#2792, #3003, #3160, #3238)

Setting --packages=external tells esbuild to make all import paths external when they look like a package path. For example, an import of ./foo/bar is not a package path and won't be external while an import of foo/bar is a package path and will be external. However, the paths field in tsconfig.json allows you to create import paths that look like package paths but that do not resolve to packages. People do not want these paths to count as package paths. So with this release, the behavior of --packages=external has been changed to happen after the tsconfig.json path remapping step.
Use the local-css loader for .module.css files by default (#20)

With this release the css loader is still used for .css files except that .module.css files now use the local-css loader. This is a common convention in the web development community. If you need .module.css files to use the css loader instead, then you can override this behavior with --loader:.module.css=css.

`v0.18.20`

Compare Source

Support advanced CSS @import rules (#953, #3137)

CSS @import statements have been extended to allow additional trailing tokens after the import path. These tokens sort of make the imported file behave as if it were wrapped in a @layer, @supports, and/or @media rule. Here are some examples:
```
@&#8203;import url(foo.css);
@&#8203;import url(foo.css) layer;
@&#8203;import url(foo.css) layer(bar);
@&#8203;import url(foo.css) layer(bar) supports(display: flex);
@&#8203;import url(foo.css) layer(bar) supports(display: flex) print;
@&#8203;import url(foo.css) layer(bar) print;
@&#8203;import url(foo.css) supports(display: flex);
@&#8203;import url(foo.css) supports(display: flex) print;
@&#8203;import url(foo.css) print;
```
You can read more about this advanced syntax here. With this release, esbuild will now bundle @import rules with these trailing tokens and will wrap the imported files in the corresponding rules. Note that this now means a given imported file can potentially appear in multiple places in the bundle. However, esbuild will still only load it once (e.g. on-load plugins will only run once per file, not once per import).

`v0.18.19`

Compare Source

Implement composes from CSS modules (#20)

This release implements the composes annotation from the CSS modules specification. It provides a way for class selectors to reference other class selectors (assuming you are using the local-css loader). And with the from syntax, this can even work with local names across CSS files. For example:
```
// app.js
import { submit } from './style.css'
const div = document.createElement('div')
div.className = submit
document.body.appendChild(div)
```
```
/* style.css */
.button {
  composes: pulse from "anim.css";
  display: inline-block;
}
.submit {
  composes: button;
  font-weight: bold;
}
```
```
/* anim.css */
@&#8203;keyframes pulse {
  from, to { opacity: 1 }
  50% { opacity: 0.5 }
}
.pulse {
  animation: 2s ease-in-out infinite pulse;
}
```
Bundling this with esbuild using --bundle --outdir=dist --loader:.css=local-css now gives the following:
```
(() => {
  // style.css
  var submit = "anim_pulse style_button style_submit";

  // app.js
  var div = document.createElement("div");
  div.className = submit;
  document.body.appendChild(div);
})();
```
```
/* anim.css */
@&#8203;keyframes anim_pulse {
  from, to {
    opacity: 1;
  }
  50% {
    opacity: 0.5;
  }
}
.anim_pulse {
  animation: 2s ease-in-out infinite anim_pulse;
}

/* style.css */
.style_button {
  display: inline-block;
}
.style_submit {
  font-weight: bold;
}
```
Import paths in the composes: ... from syntax are resolved using the new composes-from import kind, which can be intercepted by plugins during import path resolution when bundling is enabled.

Note that the order in which composed CSS classes from separate files appear in the bundled output file is deliberately undefined by design (see the specification for details). You are not supposed to declare the same CSS property in two separate class selectors and then compose them together. You are only supposed to compose CSS class selectors that declare non-overlapping CSS properties.

Issue #20 (the issue tracking CSS modules) is esbuild's most-upvoted issue! With this change, I now consider esbuild's implementation of CSS modules to be complete. There are still improvements to make and there may also be bugs with the current implementation, but these can be tracked in separate issues.
Fix non-determinism with tsconfig.json and symlinks (#3284)

This release fixes an issue that could cause esbuild to sometimes emit incorrect build output in cases where a file under the effect of tsconfig.json is inconsistently referenced through a symlink. It can happen when using npm link to create a symlink within node_modules to an unpublished package. The build result was non-deterministic because esbuild runs module resolution in parallel and the result of the tsconfig.json lookup depended on whether the import through the symlink or not through the symlink was resolved first. This problem was fixed by moving the realpath operation before the tsconfig.json lookup.
Add a hash property to output files (#3084, #3293)

As a convenience, every output file in esbuild's API now includes a hash property that is a hash of the contents field. This is the hash that's used internally by esbuild to detect changes between builds for esbuild's live-reload feature. You may also use it to detect changes between your own builds if its properties are sufficient for your use case.

This feature has been added directly to output file objects since it's just a hash of the contents field, so it makes conceptual sense to store it in the same location. Another benefit of putting it there instead of including it as a part of the watch mode API is that it can be used without watch mode enabled. You can use it to compare the output of two independent builds that were done at different times.

The hash algorithm (currently XXH64) is implementation-dependent and may be changed at any time in between esbuild versions. If you don't like esbuild's choice of hash algorithm then you are welcome to hash the contents yourself instead. As with any hash algorithm, note that while two different hashes mean that the contents are different, two equal hashes do not necessarily mean that the contents are equal. You may still want to compare the contents in addition to the hashes to detect with certainty when output files have been changed.
Avoid generating duplicate prefixed declarations in CSS (#3292)

There was a request for esbuild's CSS prefixer to avoid generating a prefixed declaration if a declaration by that name is already present in the same rule block. So with this release, esbuild will now avoid doing this:
```
/* Original code */
body {
  backdrop-filter: blur(30px);
  -webkit-backdrop-filter: blur(45px);
}

/* Old output (with --target=safari12) */
body {
  -webkit-backdrop-filter: blur(30px);
  backdrop-filter: blur(30px);
  -webkit-backdrop-filter: blur(45px);
}

/* New output (with --target=safari12) */
body {
  backdrop-filter: blur(30px);
  -webkit-backdrop-filter: blur(45px);
}
```
This can result in a visual difference in certain cases (for example if the browser understands blur(30px) but not blur(45px), it will be able to fall back to blur(30px)). But this change means esbuild now matches the behavior of Autoprefixer which is probably a good representation of how people expect this feature to work.

`v0.18.18`

Compare Source

Fix asset references with the --line-limit flag (#3286)

The recently-released --line-limit flag tells esbuild to terminate long lines after they pass this length limit. This includes automatically wrapping long strings across multiple lines using escaped newline syntax. However, using this could cause esbuild to generate incorrect code for references from generated output files to assets in the bundle (i.e. files loaded with the file or copy loaders). This is because esbuild implements asset references internally using find-and-replace with a randomly-generated string, but the find operation fails if the string is split by an escaped newline due to line wrapping. This release fixes the problem by not wrapping these strings. This issue affected asset references in both JS and CSS files.

Support local names in CSS for @keyframe, @counter-style, and @container (#20)

This release extends support for local names in CSS files loaded with the local-css loader to cover the @keyframe, @counter-style, and @container rules (and also animation, list-style, and container declarations). Here's an example:

@&#8203;keyframes pulse {
  from, to { opacity: 1 }
  50% { opacity: 0.5 }
}
@&#8203;counter-style moon {
  system: cyclic;
  symbols: 🌕 🌖 🌗 🌘 🌑 🌒 🌓 🌔;
}
@&#8203;container squish {
  li { float: left }
}
ul {
  animation: 2s ease-in-out infinite pulse;
  list-style: inside moon;
  container: squish / size;
}

With the local-css loader enabled, that CSS will be turned into something like this (with the local name mapping exposed to JS):

@&#8203;keyframes stdin_pulse {
  from, to {
    opacity: 1;
  }
  50% {
    opacity: 0.5;
  }
}
@&#8203;counter-style stdin_moon {
  system: cyclic;
  symbols: 🌕 🌖 🌗 🌘 🌑 🌒 🌓 🌔;
}
@&#8203;container stdin_squish {
  li {
    float: left;
  }
}
ul {
  animation: 2s ease-in-out infinite stdin_pulse;
  list-style: inside stdin_moon;
  container: stdin_squish / size;
}

If you want to use a global name within a file loaded with the local-css loader, you can use a :global selector to do that:

div {
  /* All symbols are global inside this scope (i.e.
   * "pulse", "moon", and "squish" are global below) */
  :global {
    animation: 2s ease-in-out infinite pulse;
    list-style: inside moon;
    container: squish / size;
  }
}

If you want to use @keyframes, @counter-style, or @container with a global name, make sure it's in a file that uses the css or global-css loader instead of the local-css loader. For example, you can configure --loader:.module.css=local-css so that the local-css loader only applies to *.module.css files.

Support strings as keyframe animation names in CSS (#2555)

With this release, esbuild will now parse animation names that are specified as strings and will convert them to identifiers. The CSS specification allows animation names to be specified using either identifiers or strings but Chrome only understands identifiers, so esbuild will now always convert string names to identifier names for Chrome compatibility:

/* Original code */
@&#8203;keyframes "hide menu" {
  from { opacity: 1 }
  to { opacity: 0 }
}
menu.hide {
  animation: 0.5s ease-in-out "hide menu";
}

/* Old output */
@&#8203;keyframes "hide menu" { from { opacity: 1 } to { opacity: 0 } }
menu.hide {
  animation: 0.5s ease-in-out "hide menu";
}

/* New output */
@&#8203;keyframes hide\ menu {
  from {
    opacity: 1;
  }
  to {
    opacity: 0;
  }
}
menu.hide {
  animation: 0.5s ease-in-out hide\ menu;
}

`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 {}
```

`v0.18.16`

Compare Source

Fix a regression with whitespace inside :is() (#3265)

The change to parse the contents of :is() in version 0.18.14 introduced a regression that incorrectly flagged the contents as a syntax error if the contents started with a whitespace token (for example div:is( .foo ) {}). This regression has been fixed.

fastify/fastify (fastify)