⬆️ Bump cross-env from 7.0.3 to 10.1.0
Bumps cross-env from 7.0.3 to 10.1.0.
Release notes
Sourced from cross-env's releases.
v10.1.0
10.1.0 (2025-09-29)
Features
- add support for default value syntax (152ae6a)
For example:
"dev:server": "cross-env wrangler dev --port ${PORT:-8787}",If
PORTis already set, use that value, otherwise fallback to8787.Learn more about Shell Parameter Expansion
v10.0.0
10.0.0 (2025-07-25)
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/configfor 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).
Commits
152ae6afeat: add support ofr default value syntaxbd70d1achore: upgrade zshy8e0b190chore(ci): get coverage8635e80fix(release): manually release a major version3a58f22chore: fix npmrc registryb70bfffchore(ci): add names to steps and workflowscc5759dfix(release): manually release a major version080a859chore: remove publish script31e5bc7chore(ci): restore built files81e9c34chore(ci): add back semantic-release- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency -
@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
This PR is stale because it has been open for more than 14 days with no activity. Remove stale label or comment or this will be closed in 14 days.