chore(deps): update devdependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/node (source)	~18.15.3 -> ~18.15.10
esbuild	~0.17.12 -> ~0.17.14
eslint-config-prettier	~8.7.0 -> ~8.8.0
glob	~9.3.0 -> ~9.3.2
rimraf	~4.4.0 -> ~4.4.1
tsx	~3.12.5 -> ~3.12.6
vite (source)	~4.2.0 -> ~4.2.1

---

Release Notes

evanw/esbuild

v0.17.14

Compare Source

• Allow the TypeScript 5.0 const modifier in object type declarations (#​3021)

  The new TypeScript 5.0 const modifier was added to esbuild in version 0.17.5, and works with classes, functions, and arrow expressions. However, support for it wasn't added to object type declarations (e.g. interfaces) due to an oversight. This release adds support for these cases, so the following TypeScript 5.0 code can now be built with esbuild:

  interface Foo { <const T>(): T }
  type Bar = { new <const T>(): T }

• Implement preliminary lowering for CSS nesting (#​1945)

  Chrome has implemented the new CSS nesting specification in version 112, which is currently in beta but will become stable very soon. So CSS nesting is now a part of the web platform!

  This release of esbuild can now transform nested CSS syntax into non-nested CSS syntax for older browsers. The transformation relies on the :is() pseudo-class in many cases, so the transformation is only guaranteed to work when targeting browsers that support :is() (e.g. Chrome 88+). You'll need to set esbuild's target to the browsers you intend to support to tell esbuild to do this transformation. You will get a warning if you use CSS nesting syntax with a target which includes older browsers that don't support :is().

  The lowering transformation looks like this:

  /* Original input */
  a.btn {
    color: #​333;
    &:hover { color: #​444 }
    &:active { color: #​555 }
  }
  
  /* New output (with --target=chrome88) */
  a.btn {
    color: #​333;
  }
  a.btn:hover {
    color: #​444;
  }
  a.btn:active {
    color: #​555;
  }

  More complex cases may generate the :is() pseudo-class:

  /* Original input */
  div, p {
    .warning, .error {
      padding: 20px;
    }
  }
  
  /* New output (with --target=chrome88) */
  :is(div, p) :is(.warning, .error) {
    padding: 20px;
  }

  In addition, esbuild now has a special warning message for nested style rules that start with an identifier. This isn't allowed in CSS because the syntax would be ambiguous with the existing declaration syntax. The new warning message looks like this:

  ▲ [WARNING] A nested style rule cannot start with "p" because it looks like the start of a declaration [css-syntax-error]
  
      <stdin>:1:7:
        1 │ main { p { margin: auto } }
          │        ^
          ╵        :is(p)
  
    To start a nested style rule with an identifier, you need to wrap the identifier in ":is(...)" to
    prevent the rule from being parsed as a declaration.
  

  Keep in mind that the transformation in this release is a preliminary implementation. CSS has many features that interact in complex ways, and there may be some edge cases that don't work correctly yet.

• Minification now removes unnecessary & CSS nesting selectors

  This release introduces the following CSS minification optimizations:

  /* Original input */
  a {
    font-weight: bold;
    & {
      color: blue;
    }
    & :hover {
      text-decoration: underline;
    }
  }
  
  /* Old output (with --minify) */
  a{font-weight:700;&{color:#​00f}& :hover{text-decoration:underline}}
  
  /* New output (with --minify) */
  a{font-weight:700;:hover{text-decoration:underline}color:#​00f}

• Minification now removes duplicates from CSS selector lists

  This release introduces the following CSS minification optimization:

  /* Original input */
  div, div { color: red }
  
  /* Old output (with --minify) */
  div,div{color:red}
  
  /* New output (with --minify) */
  div{color:red}

v0.17.13

Compare Source

• Work around an issue with NODE_PATH and Go's WebAssembly internals (#​3001)

  Go's WebAssembly implementation returns EINVAL instead of ENOTDIR when using the readdir syscall on a file. This messes up esbuild's implementation of node's module resolution algorithm since encountering ENOTDIR causes esbuild to continue its search (since it's a normal condition) while other encountering other errors causes esbuild to fail with an I/O error (since it's an unexpected condition). You can encounter this issue in practice if you use node's legacy NODE_PATH feature to tell esbuild to resolve node modules in a custom directory that was not installed by npm. This release works around this problem by converting EINVAL into ENOTDIR for the readdir syscall.

• Fix a minification bug with CSS @layer rules that have parsing errors (#​3016)

  CSS at-rules require either a {} block or a semicolon at the end. Omitting both of these causes esbuild to treat the rule as an unknown at-rule. Previous releases of esbuild had a bug that incorrectly removed unknown at-rules without any children during minification if the at-rule token matched an at-rule that esbuild can handle. Specifically cssnano can generate @layer rules with parsing errors, and empty @layer rules cannot be removed because they have side effects (@layer didn't exist when esbuild's CSS support was added, so esbuild wasn't written to handle this). This release changes esbuild to no longer discard @layer rules with parsing errors when minifying (the rule @layer c has a parsing error):

  /* Original input */
  @​layer a {
    @​layer b {
      @​layer c
    }
  }
  
  /* Old output (with --minify) */
  @​layer a.b;
  
  /* New output (with --minify) */
  @​layer a.b.c;

• Unterminated strings in CSS are no longer an error

  The CSS specification provides rules for handling parsing errors. One of those rules is that user agents must close strings upon reaching the end of a line (i.e., before an unescaped line feed, carriage return or form feed character), but then drop the construct (declaration or rule) in which the string was found. For example:

  p {
    color: green;
    font-family: 'Courier New Times
    color: red;
    color: green;
  }

  ...would be treated the same as:

  p { color: green; color: green; }

  ...because the second declaration (from font-family to the semicolon after color: red) is invalid and is dropped.

  Previously using this CSS with esbuild failed to build due to a syntax error, even though the code can be interpreted by a browser. With this release, the code now produces a warning instead of an error, and esbuild prints the invalid CSS such that it stays invalid in the output:

  /* esbuild's new non-minified output: */
  p {
    color: green;
    font-family: 'Courier New Times
    color: red;
    color: green;
  }

  /* esbuild's new minified output: */
  p{font-family:'Courier New Times
  color: red;color:green}

prettier/eslint-config-prettier

v8.8.0

Compare Source

• Added: [@​typescript-eslint/lines-around-comment]. Thanks to @​ttionya!

isaacs/node-glob

v9.3.2

Compare Source

v9.3.1

Compare Source

isaacs/rimraf

v4.4.1

Compare Source

esbuild-kit/tsx

v3.12.6

Compare Source

Bug Fixes

• repl: suppress autocomplete transformation errors (#​205) (8e1958d)

vitejs/vite

v4.2.1

Compare Source

• fix: add virtual: to virtual module source map ignore (#​12444) (c4aa28f), closes #​12444
• fix(css): inject source content conditionally (#​12449) (3e665f6), closes #​12449
• fix(worker): using data URLs for inline shared worker (#​12014) (79a5007), closes #​12014
• chore: changelog edits for 4.2 (#​12438) (ce047e3), closes #​12438

---

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.

[codecov]

Codecov Report

Merging #1979 (3646fcf) into next (27b908d) will increase coverage by 0.00%.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             next    #1979   +/-   ##
=======================================
  Coverage   99.63%   99.63%           
=======================================
  Files        2384     2384           
  Lines      238992   238992           
  Branches     1227     1230    +3     
=======================================
+ Hits       238108   238110    +2     
+ Misses        862      860    -2     
  Partials       22       22           

see 1 file with indirect coverage changes