unjs / nitro-deploys

Continues Nitro deployments for end-to-end testing deployment providers.
https://nitro.unjs.io
49 stars 9 forks source link

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

Closed renovate[bot] closed 11 months ago

renovate[bot] commented 11 months ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
esbuild ^0.19.3 -> ^0.19.5 age adoption passing confidence
h3 ^1.8.1 -> ^1.8.2 age adoption passing confidence
pnpm (source) 8.7.6 -> 8.10.0 age adoption passing confidence
ufo ^1.3.0 -> ^1.3.1 age adoption passing confidence

Release Notes

evanw/esbuild (esbuild) ### [`v0.19.5`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0195) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.19.4...v0.19.5) - Fix a regression in 0.19.0 regarding `paths` in `tsconfig.json` ([#​3354](https://togithub.com/evanw/esbuild/issues/3354)) The fix in esbuild version 0.19.0 to process `tsconfig.json` aliases before the `--packages=external` setting unintentionally broke an edge case in esbuild's handling of certain `tsconfig.json` aliases where there are multiple files with the same name in different directories. This release adjusts esbuild's behavior for this edge case so that it passes while still processing aliases before `--packages=external`. Please read the linked issue for more details. - Fix a CSS `font` property minification bug ([#​3452](https://togithub.com/evanw/esbuild/issues/3452)) This release fixes a bug where esbuild's CSS minifier didn't insert a space between the font size and the font family in the `font` CSS shorthand property in the edge case where the original source code didn't already have a space and the leading string token was shortened to an identifier: ```css /* Original code */ .foo { font: 16px"Menlo"; } /* Old output (with --minify) */ .foo{font:16pxMenlo} /* New output (with --minify) */ .foo{font:16px Menlo} ``` - Fix bundling CSS with asset names containing spaces ([#​3410](https://togithub.com/evanw/esbuild/issues/3410)) Assets referenced via CSS `url()` tokens may cause esbuild to generate invalid output when bundling if the file name contains spaces (e.g. `url(image 2.png)`). With this release, esbuild will now quote all bundled asset references in `url()` tokens to avoid this problem. This only affects assets loaded using the `file` and `copy` loaders. - Fix invalid CSS `url()` tokens in `@import` rules ([#​3426](https://togithub.com/evanw/esbuild/issues/3426)) In the future, CSS `url()` tokens may contain additional stuff after the URL. This is irrelevant today as no CSS specification does this. But esbuild previously had a bug where using these tokens in an `@import` rule resulted in malformed output. This bug has been fixed. - Fix `browser` + `false` + `type: module` in `package.json` ([#​3367](https://togithub.com/evanw/esbuild/issues/3367)) The `browser` field in `package.json` allows you to map a file to `false` to have it be treated as an empty file when bundling for the browser. However, if `package.json` contains `"type": "module"` then all `.js` files will be considered ESM, not CommonJS. Importing a named import from an empty CommonJS file gives you undefined, but importing a named export from an empty ESM file is a build error. This release changes esbuild's interpretation of these files mapped to `false` in this situation from ESM to CommonJS to avoid generating build errors for named imports. - Fix a bug in top-level await error reporting ([#​3400](https://togithub.com/evanw/esbuild/issues/3400)) Using `require()` on a file that contains [top-level await](https://v8.dev/features/top-level-await) is not allowed because `require()` must return synchronously and top-level await makes that impossible. You will get a build error if you try to bundle code that does this with esbuild. This release fixes a bug in esbuild's error reporting code for complex cases of this situation involving multiple levels of imports to get to the module containing the top-level await. - Update to Unicode 15.1.0 The character tables that determine which characters form valid JavaScript identifiers have been updated from Unicode version 15.0.0 to the newly-released Unicode version 15.1.0. I'm not putting an example in the release notes because all of the new characters will likely just show up as little squares since fonts haven't been updated yet. But you can read https://www.unicode.org/versions/Unicode15.1.0/#Summary for more information about the changes. This upgrade was contributed by [@​JLHwung](https://togithub.com/JLHwung). ### [`v0.19.4`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0194) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.19.3...v0.19.4) - Fix printing of JavaScript decorators in tricky cases ([#​3396](https://togithub.com/evanw/esbuild/issues/3396)) This release fixes some bugs where esbuild's pretty-printing of JavaScript decorators could incorrectly produced code with a syntax error. The problem happened because esbuild sometimes substitutes identifiers for other expressions in the pretty-printer itself, but the decision about whether to wrap the expression or not didn't account for this. Here are some examples: ```js // Original code import { constant } from './constants.js' import { imported } from 'external' import { undef } from './empty.js' class Foo { @​constant() @​imported() @​undef() foo } // Old output (with --bundle --format=cjs --packages=external --minify-syntax) var import_external = require("external"); var Foo = class { @​123() @​(0, import_external.imported)() @​(void 0)() foo; }; // New output (with --bundle --format=cjs --packages=external --minify-syntax) var import_external = require("external"); var Foo = class { @​(123()) @​((0, import_external.imported)()) @​((void 0)()) foo; }; ``` - Allow pre-release versions to be passed to `target` ([#​3388](https://togithub.com/evanw/esbuild/issues/3388)) People want to be able to pass version numbers for unreleased versions of node (which have extra stuff after the version numbers) to esbuild's `target` setting and have esbuild do something reasonable with them. These version strings are of course not present in esbuild's internal feature compatibility table because an unreleased version has not been released yet (by definition). With this release, esbuild will now attempt to accept these version strings passed to `target` and do something reasonable with them.
unjs/h3 (h3) ### [`v1.8.2`](https://togithub.com/unjs/h3/blob/HEAD/CHANGELOG.md#v182) [Compare Source](https://togithub.com/unjs/h3/compare/v1.8.1...v1.8.2) [compare changes](https://togithub.com/unjs/h3/compare/v1.8.1...v1.8.2) ##### 🩹 Fixes - **getRequestProtocol:** Conditionaly check `connection?.encrypted` ([#​532](https://togithub.com/unjs/h3/pull/532)) ##### 🏡 Chore - Update playground dependency ([90f64e9](https://togithub.com/unjs/h3/commit/90f64e9)) - Update lockfile ([4994334](https://togithub.com/unjs/h3/commit/4994334)) - Revert codecov-action to v3 ([de01f41](https://togithub.com/unjs/h3/commit/de01f41)) - Update dependencies ([d18f56b](https://togithub.com/unjs/h3/commit/d18f56b)) - Fix type issue with unenv ([498a540](https://togithub.com/unjs/h3/commit/498a540)) - Apply automated lint fixes ([0610b52](https://togithub.com/unjs/h3/commit/0610b52)) ##### ❤️ Contributors - Pooya Parsa ([@​pi0](http://github.com/pi0)) - Michael J. Roberts
pnpm/pnpm (pnpm) ### [`v8.10.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.10.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.9.2...v8.10.0) #### Minor Changes - Support for multiple architectures when installing dependencies [#​5965](https://togithub.com/pnpm/pnpm/issues/5965). You can now specify architectures for which you'd like to install optional dependencies, even if they don't match the architecture of the system running the install. Use the `supportedArchitectures` field in `package.json` to define your preferences. For example, the following configuration tells pnpm to install optional dependencies for Windows x64: ```json { "pnpm": { "supportedArchitectures": { "os": ["win32"], "cpu": ["x64"] } } } ``` Whereas this configuration will have pnpm install optional dependencies for Windows, macOS, and the architecture of the system currently running the install. It includes artifacts for both x64 and arm64 CPUs: ```json { "pnpm": { "supportedArchitectures": { "os": ["win32", "darwin", "current"], "cpu": ["x64", "arm64"] } } } ``` Additionally, `supportedArchitectures` also supports specifying the `libc` of the system. - The `pnpm licenses list` command now accepts the `--filter` option to check the licenses of the dependencies of a subset of workspace projects [#​5806](https://togithub.com/pnpm/pnpm/issues/5806). #### Patch Changes - Allow scoped name as bin name [#​7112](https://togithub.com/pnpm/pnpm/issues/7112). - When running scripts recursively inside a workspace, the logs of the scripts are grouped together in some CI tools. (Only works with `--workspace-concurrency 1`) - Print a warning when installing a dependency from a non-existent directory [#​7159](https://togithub.com/pnpm/pnpm/issues/7159) - Should fetch dependency from tarball url when patching dependency installed from git [#​7196](https://togithub.com/pnpm/pnpm/issues/7196) - `pnpm setup` should add a newline at the end of the updated shell config file [#​7227](https://togithub.com/pnpm/pnpm/issues/7227). - Improved the performance of linking bins of hoisted dependencies to `node_modules/.pnpm/node_modules/.bin` [#​7212](https://togithub.com/pnpm/pnpm/pull/7212). - Wrongful ELIFECYCLE error on program termination [#​7164](https://togithub.com/pnpm/pnpm/issues/7164). - `pnpm publish` should not pack the same file twice sometimes [#​6997](https://togithub.com/pnpm/pnpm/issues/6997). The fix was to update `npm-packlist` to the latest version. #### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.9.2`](https://togithub.com/pnpm/pnpm/releases/tag/v8.9.2) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.9.1...v8.9.2) ##### Patch Changes - Don't use reflink on Windows [#​7186](https://togithub.com/pnpm/pnpm/issues/7186). - Do not run node-gyp rebuild if `preinstall` lifecycle script is present [#​7206](https://togithub.com/pnpm/pnpm/pull/7206). ##### Our Gold Sponsors
##### Our Silver Sponsors
### [`v8.9.1`](https://togithub.com/pnpm/pnpm/releases/tag/v8.9.1) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.9.0...v8.9.1) ##### Patch Changes - Optimize selection result output of `pnpm update --interactive` [7109](https://togithub.com/pnpm/pnpm/issues/7109) - When `shared-workspace-lockfile` is set to `false`, read the pnpm settings from `package.json` files that are nested. This was broken in pnpm v8.9.0 [#​7184](https://togithub.com/pnpm/pnpm/issues/7184). - Fix file cloning to `node_modules` on Windows Dev Drives [#​7186](https://togithub.com/pnpm/pnpm/issues/7186). This is a fix to a regression that was shipped with v8.9.0. - `pnpm dlx` should ignore any settings that are in a `package.json` file found in the current working directory [#​7198](https://togithub.com/pnpm/pnpm/issues/7198). ##### Our Gold Sponsors
##### Our Silver Sponsors
### [`v8.9.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.9.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.8.0...v8.9.0) #### Minor Changes - **🚀Performance improvement:** Use reflinks instead of hard links by default on macOS and Windows Dev Drives [#​5001](https://togithub.com/pnpm/pnpm/issues/5001). - The list of packages that are allowed to run installation scripts now may be provided in a separate configuration file. The path to the file should be specified via the `pnpm.onlyBuiltDependenciesFile` field in `package.json`. For instance: ```json { "dependencies": { "@​my-org/policy": "1.0.0" } "pnpm": { "onlyBuiltDependenciesFile": "node_modules/@​my-org/policy/allow-build.json" } } ``` In the example above, the list is loaded from a dependency. The JSON file with the list should contain an array of package names. For instance: ```json ["esbuild", "@​reflink/reflink"] ``` With the above list, only `esbuild` and `@reflink/reflink` will be allowed to run scripts during installation. Related issue: [#​7137](https://togithub.com/pnpm/pnpm/issues/7137). - Add `disallow-workspace-cycles` option to error instead of warn about cyclic dependencies - Allow `env rm` to remove multiple node versions at once, and introduce `env add` for installing node versions without setting as default [#​7155](https://togithub.com/pnpm/pnpm/pull/7155). #### Patch Changes - Fix memory error in `pnpm why` when the dependencies tree is too big, the command will now prune the tree to just 10 end leafs and now supports `--depth` argument [#​7122](https://togithub.com/pnpm/pnpm/pull/7122). - Use `neverBuiltDependencies` and `onlyBuiltDependencies` from the root `package.json` of the workspace, when `shared-workspace-lockfile` is set to `false` [#​7141](https://togithub.com/pnpm/pnpm/pull/7141). - Optimize peers resolution to avoid out-of-memory exceptions in some rare cases, when there are too many circular dependencies and peer dependencies [#​7149](https://togithub.com/pnpm/pnpm/pull/7149). - Instead of `pnpm.overrides` replacing `resolutions`, the two are now merged. This is intended to make it easier to migrate from Yarn by allowing one to keep using `resolutions` for Yarn, but adding additional changes just for pnpm using `pnpm.overrides`. #### Our Gold Sponsors
#### Our Silver Sponsors
### [`v8.8.0`](https://togithub.com/pnpm/pnpm/releases/tag/v8.8.0) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.7.6...v8.8.0) #### Minor Changes - Add `--reporter-hide-prefix` option for `run` command to hide project name as prefix for lifecycle log outputs of running scripts [#​7061](https://togithub.com/pnpm/pnpm/issues/7061). #### Patch Changes - Pass through the `--ignore-scripts` command to install, when running `pnpm dedupe --ignore-scripts` [#​7102](https://togithub.com/pnpm/pnpm/issues/7102). - Throw meaningful error for config sub commands[#​7106](https://togithub.com/pnpm/pnpm/issues/7106). - When the `node-linker` is set to `hoisted`, the `package.json` files of the existing dependencies inside `node_modules` will be checked to verify their actual versions. The data in the `node_modules/.modules.yaml` and `node_modules/.pnpm/lock.yaml` may not be fully reliable, as an installation may fail after changes to dependencies were made but before those state files were updated [#​7107](https://togithub.com/pnpm/pnpm/pull/7107). - Don't update git-hosted dependencies when adding an unrelated dependency [#​7008](https://togithub.com/pnpm/pnpm/issues/7008). #### Our Gold Sponsors
#### Our Silver Sponsors
unjs/ufo (ufo) ### [`v1.3.1`](https://togithub.com/unjs/ufo/blob/HEAD/CHANGELOG.md#v131) [Compare Source](https://togithub.com/unjs/ufo/compare/v1.3.0...v1.3.1) [compare changes](https://togithub.com/unjs/ufo/compare/v1.3.0...v1.3.1) ##### 🩹 Fixes - Test script protocols insensitively ([#​180](https://togithub.com/unjs/ufo/pull/180)) ##### 🏡 Chore - Update dependencies ([20e99e7](https://togithub.com/unjs/ufo/commit/20e99e7)) ##### ❤️ Contributors - Pooya Parsa ([@​pi0](http://github.com/pi0)) - Daniel Roe

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.



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

netlify[bot] commented 11 months ago

Deploy Preview for nitro-deployment ready!

Name Link
Latest commit aadd576a67b7bad9d2659c50b37e9afe0fcca0f9
Latest deploy log https://app.netlify.com/sites/nitro-deployment/deploys/653bed4524360b0008bdf118
Deploy Preview https://deploy-preview-88--nitro-deployment.netlify.app
Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.