Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 25, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
cross-env 7.0.3 -> 10.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 0bcb400 to 6e085f8 Compare August 8, 2025 00:51
@renovate renovate bot force-pushed the renovate/cross-env-10.x branch 10 times, most recently from c27637a to b105ae5 Compare August 18, 2025 01:11
@renovate renovate bot force-pushed the renovate/cross-env-10.x branch 5 times, most recently from e73b5fe to 3d213e4 Compare September 9, 2025 22:28
@renovate renovate bot force-pushed the renovate/cross-env-10.x branch 6 times, most recently from 4609381 to 83d988b Compare September 24, 2025 21:31
@renovate renovate bot force-pushed the renovate/cross-env-10.x branch 3 times, most recently from 89a25ac to 9aa13c8 Compare October 1, 2025 20:33
@renovate renovate bot force-pushed the renovate/cross-env-10.x branch 2 times, most recently from ee72156 to c594e5b Compare November 5, 2025 20:36
@renovate renovate bot force-pushed the renovate/cross-env-10.x branch 4 times, most recently from 2dfe8a2 to 8e3fa5c Compare November 15, 2025 18:06
@renovate renovate bot force-pushed the renovate/cross-env-10.x branch 10 times, most recently from 722deb5 to 3aab7a8 Compare December 5, 2025 06:24
@renovate renovate bot force-pushed the renovate/cross-env-10.x branch 6 times, most recently from 2411c1b to 942c049 Compare December 11, 2025 02:55
@renovate renovate bot force-pushed the renovate/cross-env-10.x branch 6 times, most recently from 4e023f1 to 4790d06 Compare December 20, 2025 05:16
@renovate renovate bot force-pushed the renovate/cross-env-10.x branch from 4790d06 to 8704297 Compare December 22, 2025 13:01
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