Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 26, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
cross-env 7.0.310.1.0 age adoption passing confidence

Release Notes

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).

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, 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

@renovate renovate bot force-pushed the renovate/cross-env-10.x branch 4 times, most recently from e416ec9 to 22a8d43 Compare August 8, 2025 00:34
@renovate renovate bot force-pushed the renovate/cross-env-10.x branch 10 times, most recently from 9adcaf4 to 621e372 Compare August 18, 2025 01:02
@renovate renovate bot force-pushed the renovate/cross-env-10.x branch 6 times, most recently from 5074b63 to 23af4fb Compare September 12, 2025 23:09
@renovate renovate bot force-pushed the renovate/cross-env-10.x branch 6 times, most recently from 85549c3 to 4198d82 Compare September 24, 2025 21:55
@renovate renovate bot force-pushed the renovate/cross-env-10.x branch 2 times, most recently from 625f7f4 to 1b39510 Compare September 29, 2025 18:36
@renovate renovate bot force-pushed the renovate/cross-env-10.x branch 4 times, most recently from b2fcb84 to 5553dc2 Compare November 19, 2025 20:42
@renovate renovate bot force-pushed the renovate/cross-env-10.x branch 10 times, most recently from 5f7fe8e to 38a83a5 Compare December 3, 2025 09:37
@renovate renovate bot force-pushed the renovate/cross-env-10.x branch 6 times, most recently from d74b1fe to 66e4bec Compare December 10, 2025 21:57
@renovate renovate bot force-pushed the renovate/cross-env-10.x branch 7 times, most recently from 6b21627 to 7ceec5d Compare December 20, 2025 05:32
@renovate renovate bot force-pushed the renovate/cross-env-10.x branch from 7ceec5d to 577cc2c Compare December 22, 2025 13:38
@renovate renovate bot force-pushed the renovate/cross-env-10.x branch from 577cc2c to 60d3ac0 Compare January 7, 2026 01:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants