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

renovate · 2023-08-12T02:04:17Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@rollup/plugin-commonjs (source)	`^25.0.3` -> `^25.0.4`
@rollup/pluginutils (source)	`^5.0.2` -> `^5.0.3`
@vercel/nft	`^0.23.0` -> `^0.23.1`
esbuild	`^0.19.0` -> `^0.19.2`
eslint (source)	`^8.46.0` -> `^8.47.0`
listhen	`^1.2.2` -> `^1.3.0`
ohash	`^1.1.2` -> `^1.1.3`
openapi-typescript (source)	`^6.4.2` -> `^6.4.5`
pnpm (source)	`8.6.11` -> `8.6.12`
rollup (source)	`^3.27.2` -> `^3.28.0`

Release Notes

rollup/plugins (@rollup/plugin-commonjs)

`v25.0.4`

Compare Source

2023-08-11

Updates

docs: update docs #1545

rollup/plugins (@rollup/pluginutils)

`v5.0.3`

Compare Source

2023-08-13

Bugfixes

fix: add current working dirctory when pattern starts with one * #1547

vercel/nft (@vercel/nft)

`v0.23.1`

Compare Source

Bug Fixes

use builtinModules from module (#358) (bcb71fd)

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.

eslint/eslint (eslint)

`v8.47.0`

Compare Source

Features

53d7508 feat: update regex for methods with thisArg (#17439) (Francesco Trotta)

Bug Fixes

631648e fix: do not report on shadowed constructors in no-new-wrappers (#17447) (Francesco Trotta)

Documentation

a766a48 docs: document lack of config file names (#17442) (James)
a1635d6 docs: Update README (GitHub Actions Bot)
47a0859 docs: update require-unicode-regexp.md as following up #17402 (#17441) (SUZUKI Sosuke)
fcdc85d docs: Update README (GitHub Actions Bot)
2a92b6c docs: update with "Specifying Parser Options" (#17435) (Cheol-Won)
d743ed3 docs: add metadata for parser/processor (#17438) (Huáng Jùnliàng)
224376c docs: Update README (GitHub Actions Bot)
a41a8e4 docs: update script names in README (#17432) (Nitin Kumar)

Chores

bf69aa6 chore: Update dependencies (#17456) (Nicholas C. Zakas)
0e45760 chore: package.json update for @eslint/js release (ESLint Jenkins)
757bfe1 chore: Remove add-to-triage (#17450) (Nicholas C. Zakas)
b066640 chore: standardize npm script names (#17431) (Nitin Kumar)
6b2410f chore: Update add-to-triage.yml (#17444) (Nicholas C. Zakas)

unjs/listhen (listhen)

`v1.3.0`

Compare Source

compare changes

🚀 Enhancements

Print qr code for public address (#89)
qr and publicURL options and --qr, --no-qr, and --public-url cli flags (#97)
public option and --host flag to disable network expose in development by default (#98)
Stackblitz auto url detection (experimental) (#99)
cli: Accept https.* options (#93)
Tunnel support via unjs/untun and cloudflared (experimental) (#102)

🔥 Performance

dev: Use @parcel/watcher whenever available (#95)

🩹 Fixes

dev: Try to resolve h3 from user node_modules first (#94)
dev: Show better error for when no compatible handler is exported (#92)

💅 Refactors

Better watcher warning message (ec92cf4)
Fix option types and handling (ad82a70)
Use consistent emojies (4b26902)
Simplify console output (e741be0)

🏡 Chore

release: V1.2.2 (fb01a23)
Update readme (4169f50)
Update readme (1a6eaac)
cli: Fix typo and avoid exposing internal util (0c55c9c)
cli: Remove accidental console log (bd2b5d6)
Update playground (1dbb809)
Update readme (b45be3f)
Update readme (10ad172)

✅ Tests

Fix order mismatch (#90)
setup: Extend certificate generation to also write ca.pem, ca-key.pem and certificate chain to files (#103)

❤️ Contributors

Pooya Parsa (@pi0)
Mastercuber <e4d33vb85@mozmail.com>
Anthony Fu <anthonyfu117@hotmail.com>

unjs/ohash (ohash)

`v1.1.3`

Compare Source

compare changes

🔥 Performance

object-hash: Avoid using array to just concatenate the string (#36)
object-hash: Avoid toString when we know that the value is already a string (#33)
object-hash: Faster isNativeFunction check (#30)
object-hash: Faster extract object type from toString (#31)
object-hash: Faster object access by avoid string concat (#32)
object-hash: Faster circular checking by using map (#34)
object-hash: Reuse default options when is not passed (#37)
object-hash: Avoid splice method to insert values (#35)

💅 Refactors

Simplify diff formatting (8e6cabc)

📖 Documentation

Improve jsdoc for objectHash() (#43)

🏡 Chore

Add benchmark scripts (#40)
Update dev dependencies (f1ab5f7)
Lint repo (cd42064)
Add autofix ci (af19f81)
Fix ts issue (68a3429)
Enable strict type checking (2ed5b67)

❤️ Contributors

Pooya Parsa (@pi0)
Owen Kieffer-Jones
Vinicius Lourenço

drwpow/openapi-typescript (openapi-typescript)

`v6.4.5`

Compare Source

Patch Changes

#1280 50441d0 Thanks @pvanagtmaal! - Fix invalid typescript for empty request bodies, fix headers being left out when response body is omitted
#1289 7f452fa Thanks @adamschoenemann! - Fixed a bug where references to types with discriminators with implicit mappings would generate incorrect types

`v6.4.4`

Compare Source

Patch Changes

#1281 ebd31ff Thanks @pvanagtmaal! - Refactor CLI path handling, fixing several bugs

`v6.4.3`

Compare Source

Patch Changes

#1287 8a9d8ed Thanks @drwpow! - Fix oneOf handling with empty object parent type

pnpm/pnpm (pnpm)

`v8.6.12`

Compare Source

Patch Changes

Make the error message friendlier when a user attempts to run a command that does not exist #6887.
pnpm patch should work correctly when shared-workspace-file is set to false #6885.
pnpm env use should retry deleting the previous Node.js executable #6587.
pnpm dlx should not print an error stack when the underlying script execution fails #6698.
When showing the download progress of large tarball files, always display the same number of digits after the decimal point #6901.
Report download progress less frequently to improve performance #6906.
pnpm install --frozen-lockfile --lockfile-only should fail if the lockfile is not up to date with the package.json files #6913.

Our Gold Sponsors

Our Silver Sponsors

rollup/rollup (rollup)

`v3.28.0`

Compare Source

2023-08-09

Features

Add a new property preliminaryFileName to generated chunks containing the file name placeholder (#5086)
Improve performance of sourcemap generation by lazily decoding mappings (#5087)

Bug Fixes

Make the code property of rendered modules in the output readonly (#5091)

Pull Requests

#5086: feat: add preliminaryFileName to OutputChunk (@lsdsjy)
#5087: perf(sourcemaps): add back lazy sourcemap decode and handling nullish mappings (@thebanjomatic)
#5091: fix: the type of RenderedModule.code is readonly (@TrickyPi)

Configuration

📅 Schedule: Branch creation - "after 2am and before 3am" (UTC), Automerge - "after 1am and before 2am" (UTC).

🚦 Automerge: Enabled.

♻ 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 · 2023-08-12T02:07:24Z

Codecov Report

Merging #1567 (6ac4ac8) into main (d52ef62) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1567   +/-   ##
=======================================
  Coverage   76.08%   76.08%           
=======================================
  Files          74       74           
  Lines        7672     7672           
  Branches      753      753           
=======================================
  Hits         5837     5837           
  Misses       1834     1834           
  Partials        1        1

vercel bot deployed to Preview August 12, 2023 02:05 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from c6f61eb to f8ed645 Compare August 13, 2023 13:44

vercel bot deployed to Preview August 13, 2023 13:46 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from f8ed645 to 6c510ae Compare August 13, 2023 21:53

vercel bot deployed to Preview August 13, 2023 21:54 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 6c510ae to 3f1c279 Compare August 14, 2023 04:35

vercel bot deployed to Preview August 14, 2023 04:36 View deployment

chore(deps): update all non-major dependencies

6ac4ac8

renovate bot force-pushed the renovate/all-minor-patch branch from 3f1c279 to 6ac4ac8 Compare August 14, 2023 07:15

vercel bot deployed to Preview August 14, 2023 07:16 View deployment

pi0 merged commit 0cebdc5 into main Aug 14, 2023
8 checks passed

pi0 deleted the renovate/all-minor-patch branch August 14, 2023 10:04

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

renovate bot commented Aug 12, 2023 •

edited

Loading

codecov bot commented Aug 12, 2023 •

edited

Loading

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

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

Conversation

renovate bot commented Aug 12, 2023 • edited Loading

Release Notes

Updates

Bugfixes

Bug Fixes

Features

Bug Fixes

Documentation

Chores

🚀 Enhancements

🔥 Performance

🩹 Fixes

💅 Refactors

🏡 Chore

✅ Tests

❤️ Contributors

🔥 Performance

💅 Refactors

📖 Documentation

🏡 Chore

❤️ Contributors

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Our Gold Sponsors

Our Silver Sponsors

Features

Bug Fixes

Pull Requests

Configuration

codecov bot commented Aug 12, 2023 • edited Loading

Codecov Report

renovate bot commented Aug 12, 2023 •

edited

Loading

codecov bot commented Aug 12, 2023 •

edited

Loading