Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 4, 2026

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@playcanvas/pcui (source) 4.6.05.4.1 age confidence
@rollup/plugin-alias (source) 5.1.16.0.0 age confidence
@rollup/plugin-node-resolve (source) 15.3.116.0.3 age confidence
concurrently 8.2.29.2.1 age confidence
cross-env 7.0.310.1.0 age confidence
globals 16.5.017.0.0 age confidence
playcanvas (source) 1.77.02.14.4 age confidence
rollup (source) 3.29.54.54.0 age confidence
rollup-plugin-import-css 3.5.84.1.2 age confidence

Release Notes

playcanvas/pcui (@​playcanvas/pcui)

v5.4.1

Compare Source

What's Changed

Full Changelog: playcanvas/pcui@v5.4.0...v5.4.1

v5.4.0

Compare Source

What's Changed

Full Changelog: playcanvas/pcui@v5.3.3...v5.4.0

v5.3.3

Compare Source

What's Changed

Full Changelog: playcanvas/pcui@v5.3.2...v5.3.3

v5.3.2

Compare Source

What's Changed

Full Changelog: playcanvas/pcui@v5.3.1...v5.3.2

v5.3.1

Compare Source

What's Changed

Full Changelog: playcanvas/pcui@v5.3.0...v5.3.1

v5.3.0

Compare Source

What's Changed

Full Changelog: playcanvas/pcui@v5.2.4...v5.3.0

v5.2.4

Compare Source

What's Changed

Full Changelog: playcanvas/pcui@v5.2.3...v5.2.4

v5.2.3

Compare Source

What's Changed

Full Changelog: playcanvas/pcui@v5.2.2...v5.2.3

v5.2.2

Compare Source

What's Changed

Full Changelog: playcanvas/pcui@v5.2.1...v5.2.2

v5.2.1

Compare Source

What's Changed

Full Changelog: playcanvas/pcui@v5.2.0...v5.2.1

v5.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: playcanvas/pcui@v5.1.0...v5.2.0

v5.1.0

Compare Source

What's Changed

Full Changelog: playcanvas/pcui@v5.0.0...v5.1.0

v5.0.0

Compare Source

Breaking Changes

What's Changed

New Contributors

Full Changelog: playcanvas/pcui@v4.6.0...v5.0.0

rollup/plugins (@​rollup/plugin-alias)

v6.0.0

2025-10-28

Breaking Changes
  • feat!: ESM only. Update Node and Rollup minimum versions (#​1926)
rollup/plugins (@​rollup/plugin-node-resolve)

v16.0.3

2025-10-13

Bugfixes
  • fix: resolve bare targets of package "imports" using export maps; avoid fileURLToPath(null) (#​1908)

v16.0.2

2025-10-04

Bugfixes
  • fix: error thrown with empty entry (#​1893)

v16.0.1

2025-03-11

Bugfixes
  • fix: add ignoreSideEffectsForRoot to exported interface (#​1841)

v16.0.0

2024-12-15

Breaking Changes
  • feat!: set development or production condition (#​1823)
open-cli-tools/concurrently (concurrently)

v9.2.1

Compare Source

What's Changed

Full Changelog: open-cli-tools/concurrently@v9.2.0...v9.2.1

v9.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: open-cli-tools/concurrently@v9.1.2...v9.2.0

v9.1.2

Compare Source

What's Changed

New Contributors

Full Changelog: open-cli-tools/concurrently@v9.1.1...v9.1.2

v9.1.1

Compare Source

What's Changed

Full Changelog: open-cli-tools/concurrently@v9.1.0...v9.1.1

v9.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: open-cli-tools/concurrently@v9.0.1...v9.1.0

v9.0.1

Compare Source

What's Changed

Full Changelog: open-cli-tools/concurrently@v9.0.0...v9.0.1

v9.0.0

Compare Source

💥 Breaking Changes

  • Dropped support for Node.js < 18.0.0.
    Older Node.js version have reached end-of-life, and certain features require new-ish JS APIs.

  • Pending commands no longer run when --max-processes is set and an interruption/kill signal is sent - #​433, #​452, #​460
    Before v9.0.0, pressing Ctrl+C when --max-processes is set meant that only those commands would receive it. Once these stopped, the pending commands would start, which in turn meant that another Ctrl+C press would be necessary to stop them, and so on.
    Similar situation applied to combining --max-processes with --kill-others/--kill-others-on-fail.

    Starting with v9.0.0, this no longer happens, as these flags and/or key presses send a signal to stop the running commands in addition to preventing new commands from running.

  • The concurrently and default exports are now the same - #​399
    It's reasonable to expect that import { concurrently } from 'concurrently' would work the same as import concurrently from 'concurrently', however this has not been the case.
    The former used to be an unconfigured version of concurrently, lacking all features that you'd get from the CLI, which was seen as a "footgun". Both are now the same function.

    If you'd like to access the unconfigured function, use import { createConcurrently } from 'concurrently' instead.

✨ New Features

  • Exponential back-off support for process restarting - #​265, #​462
    Use --restart-after exponential. Restarts happen at 2^N seconds.
  • Add prefix padding via new --pad-prefix flag - #​166, #​417, #​495
  • Specify teardown commands via new --teardown flag - #​472, #​500
  • Expand node:<script> commands to node --run <script> - #​475
  • [API only] Inter-Process Communication (ipc) - #​498
  • [API only] Make it possible to use no colors at all - #​466
  • [API only] Add a state field to Command - #​455

🐛 Bug Fixes

Other Changes

New Contributors

Full Changelog: open-cli-tools/concurrently@v8.2.2...v9.0.0

kentcdodds/cross-env (cross-env)

v10.1.0

Compare Source

Features
  • add support for default value syntax (152ae6a)

For example:

"dev:server": "cross-env wrangler dev --port ${PORT:-8787}",

If PORT is already set, use that value, otherwise fallback to 8787.

Learn more about Shell Parameter Expansion

v10.0.0

Compare Source

TL;DR: You should probably not have to change anything if:

  • You're using a modern maintained version of Node.js (v20+ is tested)
  • You're only using the CLI (most of you are as that's the intended purpose)

In this release (which should have been v8 except I had some issues with automated releases 🙈), I've updated all the things and modernized the package. This happened in #​261

Was this needed? Not really, but I just thought it'd be fun to modernize this package.

Here's the highlights of what was done.

  • Replace Jest with Vitest for testing
  • Convert all source files from .js to .ts with proper TypeScript types
  • Use zshy for ESM-only builds (removes CJS support)
  • Adopt @​epic-web/config for TypeScript, ESLint, and Prettier
  • Update to Node.js >=20 requirement
  • Remove kcd-scripts dependency
  • Add comprehensive e2e tests with GitHub Actions matrix testing
  • Update GitHub workflow with caching and cross-platform testing
  • Modernize documentation and remove outdated sections
  • Update all dependencies to latest versions
  • Add proper TypeScript declarations and exports

The tool maintains its original functionality while being completely modernized with the latest tooling and best practices

BREAKING CHANGES
  • This is a major rewrite that changes the module format from CommonJS to ESM-only. The package now requires Node.js >=20 and only exports ESM modules (not relevant in most cases).
sindresorhus/globals (globals)

v17.0.0

Compare Source

Breaking
Improvements

playcanvas/engine (playcanvas)

v2.14.4

Compare Source

Fixes

Full Changelog: playcanvas/engine@v2.14.3...v2.14.4

v2.14.3

Compare Source

Fixes

Full Changelog: playcanvas/engine@v2.14.2...v2.14.3

v2.14.2

Compare Source

Fixes
  • Fix GSplat assets by specifying anonymous cross-origin to avoid iOS security issues by @​mvaligursky in #​8235

Full Changelog: playcanvas/engine@v2.14.1...v2.14.2

v2.14.1

Compare Source

Changes

Full Changelog: playcanvas/engine@v2.14.0...v2.14.1

v2.14.0

Compare Source

Breaking Changes

  • [BREAKING] Use linear space for vertex colors in gLTF by @​LeXXik in #​8122

    Note: Projects that use vertex colors—especially those imported from FBX—may see visual changes because vertex colors are now treated as linear by default (for glTF compatibility). If your assets use gamma-encoded vertex colors, set material.vertexColorGamma = true to restore the previous appearance. This affects StandardMaterials only, ShaderMaterials are not affected.

Other changes

Fixes


Configuration

📅 Schedule: Branch creation - "on monday at 10:00am" (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/major-all-npm-dependencies branch 4 times, most recently from 7889fc0 to e331d10 Compare January 4, 2026 13:41
@renovate renovate bot force-pushed the renovate/major-all-npm-dependencies branch from e331d10 to 4182f3c Compare January 4, 2026 13:50
@willeastcott willeastcott merged commit b0423be into main Jan 4, 2026
2 checks passed
@willeastcott willeastcott deleted the renovate/major-all-npm-dependencies branch January 4, 2026 13:51
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.

1 participant