Skip to content

chore(deps): update dependency cross-env to v10#124

Closed
renovate-bot wants to merge 1 commit intogoogleapis:mainfrom
renovate-bot:renovate/cross-env-10.x
Closed

chore(deps): update dependency cross-env to v10#124
renovate-bot wants to merge 1 commit intogoogleapis:mainfrom
renovate-bot:renovate/cross-env-10.x

Conversation

@renovate-bot
Copy link
Contributor

@renovate-bot renovate-bot commented Oct 15, 2025

This PR contains the following updates:

Package Change Age Confidence
cross-env ^7.0.3 -> ^10.0.0 age 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 becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate-bot renovate-bot requested a review from a team as a code owner October 15, 2025 20:03
@dpebot
Copy link
Collaborator

dpebot commented Oct 15, 2025

/gcbrun

@renovate-bot renovate-bot force-pushed the renovate/cross-env-10.x branch from 7b2ad1d to 071b566 Compare October 21, 2025 11:33
@dpebot
Copy link
Collaborator

dpebot commented Oct 21, 2025

/gcbrun

@renovate-bot renovate-bot force-pushed the renovate/cross-env-10.x branch from 071b566 to 929bcd8 Compare October 21, 2025 21:43
@dpebot
Copy link
Collaborator

dpebot commented Oct 21, 2025

/gcbrun

@forking-renovate
Copy link

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 10.x releases. But if you manually upgrade to 10.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate-bot renovate-bot deleted the renovate/cross-env-10.x branch October 23, 2025 22:33
GautamSharda pushed a commit that referenced this pull request Oct 29, 2025
- Fix #123: introduces maxResults parameter
- Fix #124: fixed the behaviors of the streaming
  it seems better to be back of using through2.
GautamSharda pushed a commit that referenced this pull request Oct 29, 2025
- Fix #123: introduces maxResults parameter
- Fix #124: fixed the behaviors of the streaming
  it seems better to be back of using through2.
GautamSharda pushed a commit that referenced this pull request Dec 4, 2025
* chore: add deprecation notice to library
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.

3 participants