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.

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

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

Open
wants to merge 1 commit into
base: next
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 20, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@lingui/cli 5.1.2 -> 5.2.0 age adoption passing confidence
@lingui/conf 5.1.2 -> 5.2.0 age adoption passing confidence
@lingui/core 5.1.2 -> 5.2.0 age adoption passing confidence
@types/node (source) 20.14.10 -> 20.17.17 age adoption passing confidence
@warp-ds/uno 2.0.0 -> 2.0.2 age adoption passing confidence
chalk 5.3.0 -> 5.4.1 age adoption passing confidence
esbuild 0.23.0 -> 0.24.2 age adoption passing confidence
fs-extra 11.2.0 -> 11.3.0 age adoption passing confidence
glob 11.0.0 -> 11.0.1 age adoption passing confidence
nanoid 5.0.7 -> 5.0.9 age adoption passing confidence
ora 8.0.1 -> 8.2.0 age adoption passing confidence
typescript (source) 5.5.3 -> 5.7.3 age adoption passing confidence
unocss (source) 0.61.2 -> 0.65.4 age adoption passing confidence
vite (source) 5.3.3 -> 5.4.14 age adoption passing confidence
yaml (source) 2.4.5 -> 2.7.0 age adoption passing confidence

Release Notes

lingui/js-lingui (@​lingui/cli)

v5.2.0

Compare Source

Bug Fixes
Features

5.1.2 (2024-12-16)

Note: Version bump only for package js-lingui-workspaces

5.1.1 (2024-12-16)

Note: Version bump only for package js-lingui-workspaces

warp-ds/drive (@​warp-ds/uno)

v2.0.2

Compare Source

Bug Fixes

v2.0.1

Compare Source

Bug Fixes
chalk/chalk (chalk)

v5.4.1

Compare Source

v5.4.0

Compare Source

  • Update CIRCLECI environments to return level 3 color support f838120
evanw/esbuild (esbuild)

v0.24.2

Compare Source

  • Fix regression with --define and import.meta (#​4010, #​4012, #​4013)

    The previous change in version 0.24.1 to use a more expression-like parser for define values to allow quoted property names introduced a regression that removed the ability to use --define:import.meta=.... Even though import is normally a keyword that can't be used as an identifier, ES modules special-case the import.meta expression to behave like an identifier anyway. This change fixes the regression.

    This fix was contributed by @​sapphi-red.

v0.24.1

Compare Source

  • Allow es2024 as a target in tsconfig.json (#​4004)

    TypeScript recently added es2024 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:

    {
      "compilerOptions": {
        "target": "ES2024"
      }
    }

    As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.

    This fix was contributed by @​billyjanitsch.

  • Allow automatic semicolon insertion after get/set

    This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:

    class Foo {
      get
      *x() {}
      set
      *y() {}
    }

    The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.

  • Allow quoted property names in --define and --pure (#​4008)

    The define and pure API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes --define and --pure consistent with --global-name, which already supported quoted property names. For example, the following is now possible:

    // The following code now transforms to "return true;\n"
    console.log(esbuild.transformSync(
      `return process.env['SOME-TEST-VAR']`,
      { define: { 'process.env["SOME-TEST-VAR"]': 'true' } },
    ))

    Note that if you're passing values like this on the command line using esbuild's --define flag, then you'll need to know how to escape quote characters for your shell. You may find esbuild's JavaScript API more ergonomic and portable than writing shell code.

  • Minify empty try/catch/finally blocks (#​4003)

    With this release, esbuild will now attempt to minify empty try blocks:

    // Original code
    try {} catch { foo() } finally { bar() }
    
    // Old output (with --minify)
    try{}catch{foo()}finally{bar()}
    
    // New output (with --minify)
    bar();

    This can sometimes expose additional minification opportunities.

  • Include entryPoint metadata for the copy loader (#​3985)

    Almost all entry points already include a entryPoint field in the outputs map in esbuild's build metadata. However, this wasn't the case for the copy loader as that loader is a special-case that doesn't behave like other loaders. This release adds the entryPoint field in this case.

  • Source mappings may now contain null entries (#​3310, #​3878)

    With this change, sources that result in an empty source map may now emit a null source mapping (i.e. one with a generated position but without a source index or original position). This change improves source map accuracy by fixing a problem where minified code from a source without any source mappings could potentially still be associated with a mapping from another source file earlier in the generated output on the same minified line. It manifests as nonsensical files in source mapped stack traces. Now the null mapping "resets" the source map so that any lookups into the minified code without any mappings resolves to null (which appears as the output file in stack traces) instead of the incorrect source file.

    This change shouldn't affect anything in most situations. I'm only mentioning it in the release notes in case it introduces a bug with source mapping. It's part of a work-in-progress future feature that will let you omit certain unimportant files from the generated source map to reduce source map size.

  • Avoid using the parent directory name for determinism (#​3998)

    To make generated code more readable, esbuild includes the name of the source file when generating certain variable names within the file. Specifically bundling a CommonJS file generates a variable to store the lazily-evaluated module initializer. However, if a file is named index.js (or with a different extension), esbuild will use the name of the parent directory instead for a better name (since many packages have files all named index.js but have unique directory names).

    This is problematic when the bundle entry point is named index.js and the parent directory name is non-deterministic (e.g. a temporary directory created by a build script). To avoid non-determinism in esbuild's output, esbuild will now use index instead of the parent directory in this case. Specifically this will happen if the parent directory is equal to esbuild's outbase API option, which defaults to the lowest common ancestor of all user-specified entry point paths.

  • Experimental support for esbuild on NetBSD (#​3974)

    With this release, esbuild now has a published binary executable for NetBSD in the @esbuild/netbsd-arm64 npm package, and esbuild's installer has been modified to attempt to use it when on NetBSD. Hopefully this makes installing esbuild via npm work on NetBSD. This change was contributed by @​bsiegert.

    ⚠️ Note: NetBSD is not one of Node's supported platforms, so installing esbuild may or may not work on NetBSD depending on how Node has been patched. This is not a problem with esbuild. ⚠️

v0.24.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.23.0 or ~0.23.0. See npm's documentation about semver for more information.

  • Drop support for older platforms (#​3902)

    This release drops support for the following operating system:

    • macOS 10.15 Catalina

    This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

    Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:

    git clone https://github.com/evanw/esbuild.git
    cd esbuild
    go build ./cmd/esbuild
    ./esbuild --version
    
  • Fix class field decorators in TypeScript if useDefineForClassFields is false (#​3913)

    Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

  • Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#​3898)

    TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

  • Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#​3915)

    Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

  • Work around more issues with Deno 1.31+ (#​3917)

    This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

    This fix was contributed by @​Joshix-1.

v0.23.1

Compare Source

  • Allow using the node: import prefix with es* targets (#​3821)

    The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

    // Original code
    import fs from 'node:fs'
    fs.open
    
    // Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
    import fs from "fs";
    fs.open;
    
    // New output (with --bundle --format=esm --platform=node --target=node18,es2022)
    import fs from "node:fs";
    fs.open;
  • Fix a panic when using the CLI with invalid build flags if --analyze is present (#​3834)

    Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

  • Fix incorrect location of certain error messages (#​3845)

    This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

  • Print comments before case clauses in switch statements (#​3838)

    With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

  • Fix a memory leak with pluginData (#​3825)

    With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

jprichardson/node-fs-extra (fs-extra)

v11.3.0

Compare Source

isaacs/node-glob (glob)

v11.0.1

Compare Source

ai/nanoid (nanoid)

v5.0.9

Compare Source

  • Fixed a way to break Nano ID by passing non-integer size (by @​myndzi).

v5.0.8

Compare Source

sindresorhus/ora (ora)

v8.2.0

Compare Source


v8.1.1

Compare Source

  • Fix animation speed when update methods are called very often 818ca34
  • Fix handling of symbol being empty string in stopAndPersist() (#​243) 5117dfb

v8.1.0

Compare Source

microsoft/TypeScript (typescript)

v5.7.3

Compare Source

v5.7.2

Compare Source

v5.6.3

Compare Source

v5.6.2

Compare Source

v5.5.4: TypeScript 5.5.4

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

unocss/unocss (unocss)

v0.65.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.65.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.65.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v0.65.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.65.0

Compare Source

If you are interested, please read our upgrade introduction 🌟🌟🌟.
   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.64.1

Compare Source

No significant changes

    View changes on GitHub

v0.64.0

Compare Source

   🚨 Breaking Changes
   🐞 Bug Fixes
    View changes on GitHub

v0.63.6

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.63.5

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.63.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.63.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.63.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.63.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.63.0

Compare Source

   🚀 Features
   🐞 Bug Fixes

Configuration

📅 Schedule: Branch creation - "every weekend after 4am" (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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/all-dependencies-(non-major) branch 7 times, most recently from f690f76 to 9afed69 Compare July 28, 2024 10:52
@renovate renovate bot force-pushed the renovate/all-dependencies-(non-major) branch 4 times, most recently from 4eb48af to f4a1e8e Compare August 2, 2024 10:14
@renovate renovate bot force-pushed the renovate/all-dependencies-(non-major) branch 6 times, most recently from d8a4e88 to b08d8f8 Compare August 12, 2024 17:26
@renovate renovate bot force-pushed the renovate/all-dependencies-(non-major) branch 7 times, most recently from c0e4e75 to 46cc353 Compare August 20, 2024 17:06
@renovate renovate bot force-pushed the renovate/all-dependencies-(non-major) branch 4 times, most recently from 4843059 to f77a182 Compare August 28, 2024 09:16
@renovate renovate bot force-pushed the renovate/all-dependencies-(non-major) branch 2 times, most recently from b413a8a to 121b06f Compare September 3, 2024 18:03
@renovate renovate bot force-pushed the renovate/all-dependencies-(non-major) branch 2 times, most recently from 6d3e2df to ed772d4 Compare December 4, 2024 07:16
@renovate renovate bot force-pushed the renovate/all-dependencies-(non-major) branch 2 times, most recently from c5497e8 to 2ba8375 Compare December 12, 2024 14:06
@renovate renovate bot force-pushed the renovate/all-dependencies-(non-major) branch 6 times, most recently from b30d3e9 to 647cc48 Compare December 25, 2024 10:50
@renovate renovate bot force-pushed the renovate/all-dependencies-(non-major) branch from 647cc48 to 152b2ba Compare December 31, 2024 05:09
@renovate renovate bot force-pushed the renovate/all-dependencies-(non-major) branch 4 times, most recently from cdfeb4a to bf3e59e Compare January 10, 2025 10:20
@renovate renovate bot force-pushed the renovate/all-dependencies-(non-major) branch 6 times, most recently from 3aa9f69 to 179c743 Compare January 21, 2025 13:43
@renovate renovate bot force-pushed the renovate/all-dependencies-(non-major) branch 4 times, most recently from a2684bb to 7fc6036 Compare January 27, 2025 10:48
@renovate renovate bot force-pushed the renovate/all-dependencies-(non-major) branch 3 times, most recently from 5e2b7e7 to 11a2595 Compare February 2, 2025 08:39
@renovate renovate bot force-pushed the renovate/all-dependencies-(non-major) branch from 11a2595 to c3f8453 Compare February 4, 2025 02:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants