Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Merged
merged 1 commit into from
Sep 20, 2023
Merged

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

merged 1 commit into from
Sep 20, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 18, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@cloudflare/workers-types ^4.20230904.0 -> ^4.20230914.0 age adoption passing confidence
@nuxtjs/plausible ^0.2.1 -> ^0.2.3 age adoption passing confidence
@types/aws-lambda (source) ^8.10.119 -> ^8.10.121 age adoption passing confidence
@types/fs-extra (source) ^11.0.1 -> ^11.0.2 age adoption passing confidence
@types/http-proxy (source) ^1.17.11 -> ^1.17.12 age adoption passing confidence
@types/node-fetch (source) ^2.6.4 -> ^2.6.5 age adoption passing confidence
@types/semver (source) ^7.5.1 -> ^7.5.2 age adoption passing confidence
@vercel/nft ^0.23.1 -> ^0.24.1 age adoption passing confidence
@vitest/coverage-v8 (source) ^0.34.3 -> ^0.34.4 age adoption passing confidence
citty ^0.1.3 -> ^0.1.4 age adoption passing confidence
edge-runtime (source) ^2.5.1 -> ^2.5.3 age adoption passing confidence
esbuild ^0.19.2 -> ^0.19.3 age adoption passing confidence
eslint (source) ^8.48.0 -> ^8.49.0 age adoption passing confidence
httpxy ^0.1.4 -> ^0.1.5 age adoption passing confidence
listhen ^1.4.8 -> ^1.5.5 age adoption passing confidence
nuxt ^3.7.0 -> ^3.7.3 age adoption passing confidence
openapi-typescript (source) ^6.5.4 -> ^6.6.1 age adoption passing confidence
pnpm (source) 8.7.0 -> 8.7.6 age adoption passing confidence
rollup (source) ^3.29.0 -> ^3.29.2 age adoption passing confidence
undici (source) ^5.23.0 -> ^5.25.0 age adoption passing confidence
vitest ^0.34.3 -> ^0.34.4 age adoption passing confidence

Release Notes

cloudflare/workerd (@​cloudflare/workers-types)

v4.20230914.0

Compare Source

nuxt-modules/plausible (@​nuxtjs/plausible)

v0.2.3

Compare Source

No significant changes

    View changes on GitHub
vercel/nft (@​vercel/nft)

v0.24.1

Compare Source

Bug Fixes

v0.24.0

Compare Source

Features
vitest-dev/vitest (@​vitest/coverage-v8)

v0.34.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
unjs/citty (citty)

v0.1.4

Compare Source

compare changes

🚀 Enhancements
  • Support cleanup hook (#​64)
  • Add createMain utility (#​65)
  • Support --version (#​67)
🩹 Fixes
  • Do not throw error when no subcommand specified but main has run (#​58)
🏡 Chore
❤️ Contributors
vercel/edge-runtime (edge-runtime)

v2.5.3

Compare Source

Patch Changes

v2.5.2

Compare Source

Patch Changes
evanw/esbuild (esbuild)

v0.19.3

Compare Source

  • Fix list-style-type with the local-css loader (#​3325)

    The local-css loader incorrectly treated all identifiers provided to list-style-type as a custom local identifier. That included identifiers such as none which have special meaning in CSS, and which should not be treated as custom local identifiers. This release fixes this bug:

    /* Original code */
ul { list-style-type: none }

/* Old output (with --loader=local-css) */
ul {
  list-style-type: stdin_none;
}

/* New output (with --loader=local-css) */
ul {
  list-style-type: none;
}

    Note that this bug only affected code using the local-css loader. It did not affect code using the css loader.

  • Avoid inserting temporary variables before use strict (#​3322)

    This release fixes a bug where esbuild could incorrectly insert automatically-generated temporary variables before use strict directives:

    // Original code
function foo() {
  'use strict'
  a.b?.c()
}

// Old output (with --target=es6)
function foo() {
  var _a;
  "use strict";
  (_a = a.b) == null ? void 0 : _a.c();
}

// New output (with --target=es6)
function foo() {
  "use strict";
  var _a;
  (_a = a.b) == null ? void 0 : _a.c();
}

  • Adjust TypeScript enum output to better approximate tsc (#​3329)

    TypeScript enum values can be either number literals or string literals. Numbers create a bidirectional mapping between the name and the value but strings only create a unidirectional mapping from the name to the value. When the enum value is neither a number literal nor a string literal, TypeScript and esbuild both default to treating it as a number:

    // Original TypeScript code
declare const foo: any
enum Foo {
  NUMBER = 1,
  STRING = 'a',
  OTHER = foo,
}

// Compiled JavaScript code (from "tsc")
var Foo;
(function (Foo) {
  Foo[Foo["NUMBER"] = 1] = "NUMBER";
  Foo["STRING"] = "a";
  Foo[Foo["OTHER"] = foo] = "OTHER";
})(Foo || (Foo = {}));

    However, TypeScript does constant folding slightly differently than esbuild. For example, it may consider template literals to be string literals in some cases:

    // Original TypeScript code
declare const foo = 'foo'
enum Foo {
  PRESENT = `${foo}`,
  MISSING = `${bar}`,
}

// Compiled JavaScript code (from "tsc")
var Foo;
(function (Foo) {
  Foo["PRESENT"] = "foo";
  Foo[Foo["MISSING"] = `${bar}`] = "MISSING";
})(Foo || (Foo = {}));

    The template literal initializer for PRESENT is treated as a string while the template literal initializer for MISSING is treated as a number. Previously esbuild treated both of these cases as a number but starting with this release, esbuild will now treat both of these cases as a string. This doesn't exactly match the behavior of tsc but in the case where the behavior diverges tsc reports a compile error, so this seems like acceptible behavior for esbuild. Note that handling these cases completely correctly would require esbuild to parse type declarations (see the declare keyword), which esbuild deliberately doesn't do.

  • Ignore case in CSS in more places (#​3316)

    This release makes esbuild's CSS support more case-agnostic, which better matches how browsers work. For example:

    /* Original code */
@​KeyFrames Foo { From { OpaCity: 0 } To { OpaCity: 1 } }
body { CoLoR: YeLLoW }

/* Old output (with --minify) */
@​KeyFrames Foo{From {OpaCity: 0} To {OpaCity: 1}}body{CoLoR:YeLLoW}

/* New output (with --minify) */
@​KeyFrames Foo{0%{OpaCity:0}To{OpaCity:1}}body{CoLoR:#ff0}

    Please never actually write code like this.

  • Improve the error message for null entries in exports (#​3377)

    Package authors can disable package export paths with the exports map in package.json. With this release, esbuild now has a clearer error message that points to the null token in package.json itself instead of to the surrounding context. Here is an example of the new error message:

    ✘ [ERROR] Could not resolve "msw/browser"

    lib/msw-config.ts:2:28:
      2 │ import { setupWorker } from 'msw/browser';
        ╵                             ~~~~~~~~~~~~~

  The path "./browser" cannot be imported from package "msw" because it was explicitly disabled by
  the package author here:

    node_modules/msw/package.json:17:14:
      17 │       "node": null,
         ╵               ~~~~

  You can mark the path "msw/browser" as external to exclude it from the bundle, which will remove
  this error and leave the unresolved path in the bundle.

  • Parse and print the with keyword in import statements

    JavaScript was going to have a feature called "import assertions" that adds an assert keyword to import statements. It looked like this:

    import stuff from './stuff.json' assert { type: 'json' }

    The feature provided a way to assert that the imported file is of a certain type (but was not allowed to affect how the import is interpreted, even though that's how everyone expected it to behave). The feature was fully specified and then actually implemented and shipped in Chrome before the people behind the feature realized that they should allow it to affect how the import is interpreted after all. So import assertions are no longer going to be added to the language.

    Instead, the current proposal is to add a feature called "import attributes" instead that adds a with keyword to import statements. It looks like this:

    import stuff from './stuff.json' with { type: 'json' }

    This feature provides a way to affect how the import is interpreted. With this release, esbuild now has preliminary support for parsing and printing this new with keyword. The with keyword is not yet interpreted by esbuild, however, so bundling code with it will generate a build error. All this release does is allow you to use esbuild to process code containing it (such as removing types from TypeScript code). Note that this syntax is not yet a part of JavaScript and may be removed or altered in the future if the specification changes (which it already has once, as described above). If that happens, esbuild reserves the right to remove or alter its support for this syntax too.

eslint/eslint (eslint)

v8.49.0

Compare Source

Features

  • da09f4e feat: Implement onUnreachableCodePathStart/End (#​17511) (Nicholas C. Zakas)
  • 32b2327 feat: Emit deprecation warnings in RuleTester (#​17527) (Nicholas C. Zakas)
  • acb7df3 feat: add new enforce option to lines-between-class-members (#​17462) (Nitin Kumar)

Documentation

  • ecfb54f docs: Update README (GitHub Actions Bot)
  • de86b3b docs: update no-promise-executor-return examples (#​17529) (Nitin Kumar)
  • 032c4b1 docs: add typescript template (#​17500) (James)
  • cd7da5c docs: Update README (GitHub Actions Bot)

Chores

unjs/httpxy (httpxy)

v0.1.5

Compare Source

compare changes

🩹 Fixes
  • Handle client close event (#​8)
🏡 Chore
❤️ Contributors
unjs/listhen (listhen)

v1.5.5

Compare Source

compare changes

🩹 Fixes
  • Apply default localhost in internal generateURL util (6c76d31)
❤️ Contributors

v1.5.4

Compare Source

compare changes

🩹 Fixes
  • Use localhost when host is empty for getURL (9ec7d77)
📖 Documentation
🏡 Chore
❤️ Contributors
  • Pooya Parsa (@​pi0)
  • Tech Genius

v1.5.3

Compare Source

compare changes

🩹 Fixes
  • Correct private host warning message (df5ff4d)
  • Prefer explicit hostname option over HOST env (0674d96)
🏡 Chore
  • release: V1.5.2 (1aab0dd)
  • Revert to codecov/codecov-action@v3 (c911a1f)
❤️ Contributors

v1.5.2

Compare Source

compare changes

🔥 Performance
  • Imprve default host for windows, docker and wsl (#​126)
💅 Refactors
  • Use std-env for stackblitz detection (933c0c3)
❤️ Contributors

v1.5.1

Compare Source

compare changes

🩹 Fixes
🏡 Chore
❤️ Contributors

v1.5.0

Compare Source

compare changes

🚀 Enhancements
  • Trap SIGINT, SIGTERM and SIGHUP for autoclosing (#​108)
🩹 Fixes
  • Allow valid ipv6 as hostnames (78dd4b7)
🏡 Chore
❤️ Contributors
  • Mastercuber <e4d33vb85@​mozmail.com>
  • Pooya Parsa (@​pi0)
nuxt/nuxt (nuxt)

v3.7.3

Compare Source

3.7.3 is a hotfix release to address a regression introduced in 3.7.2.

👉 Changelog

compare changes

🩹 Fixes
  • nuxt: Ensure plugins retain original order (#​23174)
  • nuxt: Allow importing server components from #components (#​23188)
💅 Refactors
  • nuxt: Don't wrap server placeholders/client fallbacks (#​21980)
📖 Documentation
  • Added missing leading slash (#​23169)
  • Update internal issue decision making flowchart link (#​23162)
❤️ Contributors

v3.7.2

Compare Source

3.7.2 is a regularly scheduled patch release.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade

👉 Changelog

compare changes

🩹 Fixes
  • nuxt: Scroll to top by default on dynamic routes (#​22403)
  • nuxt: Don't joinURL with remote sources on NuxtIsland (#​23093)
  • nuxt: Exclude data-v attrs from server component props (#​23095)
  • nuxt: Handle optional params within a path segment (#​23070)
  • nuxt: Include method when creating useFetch auto key (#​23086)
  • vite: Add css to manifest without cssCodeSplit (#​23049)
  • nuxt: Find parent routes by exact path match (#​23040)
  • nuxt: Load spaLoadingTemplate if file exists (#​23048)
  • nuxt: Handle unset spa-loading fallback (#​23120)
  • kit: Improve generated tsconfig.json defaults (#​23121)
  • vite: Remove dev styles injected via absolute path (#​23126)
  • nuxt: Default scanned layer components to priority 0 (#​23127)
  • nuxt: Allow granularly overriding pages in layers (#​23134)
  • nuxt: Respect layer order for other layer plugins (#​23148)
  • nuxt: Allow changing dirs within modules (#​23133)
  • nuxt: Allow overriding components + only warn if clash (#​23156)
📖 Documentation
  • Remove 'caching' section from data fetching (fe29948fe)
  • Fix broken links on experimental features (#​23052)
  • Fix typo (#​23060)
  • Add name param to PageMeta interface description (#​23107)
  • Fix typo for experimental.componentIslands (#​23138)
  • Change NuxtLabs UI to Nuxt UI (#​23150)
  • Fix typo in nuxi init command (#​23155)
🏡 Chore
🤖 CI
❤️ Contributors

v3.7.1

Compare Source

3.7.1 is a regularly scheduled patch release.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.

👉 Changelog

compare changes

🔥 Performance
  • nuxt: Prevent head dom from rendering twice (#​22974)
  • nuxt: Decrease default bundle size (#​22999)
🩹 Fixes
  • nuxt: Exclude resolved vite virtual modules prefix (#​22834)
  • nuxt: Ensure typed layout prop persists through build (#​22855)
  • nuxt: Render server components when ssr: false (#​22869)
  • kit: Respect priority when registering components dirs (#​22882)
  • kit: Allow passing a string to addLayout (#​22902)
  • nuxt: Ensure middleware is processed when returning true (#​22905)
  • nuxt: Unpause dom updates on error (#​22945)
  • nuxt: Disallow write: false for type templates (#​22972)
  • vite: Don't set explicit conditions in shouldExternalize (#​22991)
  • nuxt: Render inlined ssr styles before stylesheets (#​22986)
  • nuxt: Improve types within plugin templates (#​22998)
  • nuxt: Load layer plugins before project plugins (#​22889)
  • nuxt: Use destr in more places over JSON.parse (#​22997)
  • nuxt: Resolve head instance from Nuxt app (#​22973)
  • nuxt: Always use increment for id with client side islands (#​22975)
📖 Documentation
  • Add info about dynamic nested routes (#​22862)
  • Update nuxt bridge migration guide (#​22815)
  • Rename nuxt-community to nuxt-modules (9991da634)
  • Add banner for readme (e92d99db3)
  • Simplify readme (681f92915)
  • Text center on banner (ea5142176)
  • Clarify that 'it' is <NuxtPage> (#​22912)
  • Update examples of dynamic pageKey (#​22920)
  • Fix types in 'server utilities' example (#​22978)
  • Describe env object for nuxt plugins (#​22963)
  • Docs/3.api/3.utils/define-page-meta.md (#​23006)
  • Accessing custom props for NuxtLayout (#​22989)
  • Add information about server component context (#​22964)
🏡 Chore
  • Fix variable name in release scripts (adb6ec674)
  • Track nuxi-edge rather than nuxi-ng (9610cf03d)
🤖 CI
  • Create 2.x release branch as well (cdf9b5547)
  • Use GITHUB_REF_NAME to get branch for release (d49ea58de)
  • Use changelogen utility to get current branch (7431e2258)
❤️ Contributors
drwpow/openapi-typescript (openapi-typescript)

v6.6.1

Compare Source

Patch Changes

v6.6.0

Compare Source

Minor Changes

v6.5.5

Compare Source

Patch Changes
pnpm/pnpm (pnpm)

v8.7.6

Compare Source

Patch Changes

  • Don't run the prepublishOnly scripts of git-hosted dependencies #​7026.
  • Fix a bug in which use-node-version or node-version isn't passed down to checkEngine when using pnpm workspace, resulting in an error #​6981.
  • Don't print out each deprecated subdependency separately with its deprecation message. Just print out a summary of all the deprecated subdependencies #​6707.
  • Fixed an ENOENT error that was sometimes happening during install with "hoisted" node_modules #​6756.

Our Gold Sponsors

Our Silver Sponsors

v8.7.5

Compare Source

Patch Changes

  • Improve performance of installation by using a worker for creating the symlinks inside node_modules/.pnpm #​7069.
  • Tarballs that have hard links are now unpacked successfully. This fixes a regression introduced in v8.7.0, which was shipped with our new in-house tarball parser #​7062.

Our Gold Sponsors

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
Copy link

codecov bot commented Sep 18, 2023 •
edited
Loading

Codecov Report

Merging #1733 (80e4890) into main (2cdb93f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1733   +/-   ##
=======================================
  Coverage   77.27%   77.27%           
=======================================
  Files          75       75           
  Lines        7911     7911           
  Branches      806      806           
=======================================
  Hits         6113     6113           
  Misses       1796     1796           
  Partials        2        2

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from e15e714 to 7ab91bf Compare September 19, 2023 18:14
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 7ab91bf to 80e4890 Compare September 20, 2023 13:53
@pi0 pi0 merged commit f1f412b into main Sep 20, 2023
@pi0 pi0 deleted the renovate/all-minor-patch branch September 20, 2023 14:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@pi0