* chore: use native stripVTControlCharacters
Since Node 16.x, there is a built-in function,
`stripVTControlCharacters`. This does the same job as the `strip-ansi`
package and makes it redundant going forward.
The minimum node version in these projects is at least 16, so we should
be good to switch.
* chore: remove unnecessary package-lock.json from import-npm fixture
* chore: remove private package from changeset
* chore: fix formatting
---------
Co-authored-by: Edmund Hung <edmund@cloudflare.com>
* modernize kv-asset-handler so that we can test is in Node 22+
* suggestion from Vic
* fix exports on the kv-asset-handler package.json
* move kv-asset-handler tests back into main test run
* only test on Node 22
Node 20 has been in Maintenance for over a year and will become end of life in April 2026.
Node 22 entered Maintenance in October and is arguably the most stable and supported version right now.
* also test packages on Node 20 and 24
* really don't run interactive-dev tests on Windows
* remove redundant service-worker-mock
* wait for the old port to be closed
* Add resilience to reading and writing the dev registry files
* give prisma tests a bit longer to run
* vite-plugin: skip containers tests locally if docker is not running
* fixtures/interactive-dev-tests: skip containers tests locally if docker is not running
* wrangler: skip containers e2e tests locally if docker is not running
* add message for tests skipping in wrangler e2es and interactive-dev-tests fixture
* run prettier
* move containers skipping logic to vite-plugin vitest global setup and add console warn
* test: further efforts to reduce flakes on email bindings
* wait for container count in interactive-dev tests to avoid flakes
* upload turbo summaries
* don't show dry-run
* fixup turbo artifacts
* run more tests, more of the time
* Checks can be single-os
* syntax
* syntax
* add more labels
* fix group
* fix group
* skip node 24
* skip test
* Simplify PR validation
* fix tool tests
* re-skip 24
* address review comments
* match existing test names
* tighten up turbo dependencies to avoid having to manually build
* test: ensure that fixture packages always start with `fixture-`
* refactor: consolidate fixture package names with consistent `fixture-` prefix
Updates all 63 fixture package names to use a consistent naming scheme with logical categorization:
- Core workers: fixture-worker-basic, fixture-worker-ai, fixture-worker-typescript, etc.
- Pages functions: fixture-pages-functions, fixture-pages-workerjs, etc.
- Database/storage: fixture-d1-basic, fixture-secrets-store, etc.
- Module handling: fixture-import-wasm, fixture-no-bundle-import, etc.
- Development tools: fixture-interactive-dev, fixture-local-mode, etc.
Also updates test files that reference specific fixture package names to maintain compatibility.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
* add CI_OS env var to the check run to ensure correct turbo remote caching
* fixup! refactor: consolidate fixture package names with consistent `fixture-` prefix
* fixup! test: ensure that fixture packages always start with `fixture-`
* revert unnecessary change
---------
Co-authored-by: Claude <noreply@anthropic.com>
* No more React in dev
* fix e2e
* remove more dead code
* fix
* fix fixtures
* fix prettier
* fix lockfile
* more dead code elimination
* lockfile
* fix regression
* Create late-guests-end.md
* fix lockfile
* fix merge
* fix snapshots
* remove stray log
* windows?
* add e2e retries
* fail at the right bit of e2e c3 test
* skip on windows
* remove retries
* Update messaging
* initial implementation
* implement higher-level interface for hotkeys
automatically compute instructions
* extract onKeyPress to own module
for mocking
* add tests
* add changeset
* add --x-dev-env flagged run of fixtures/interactive-dev-tests
* add test for handlers throwing errors
* chore: cleanup teardown
* fix: onKeyPress keeps the process alive after unregistering
Listening for events on process.stdin (eg .on('keypress')) causes it to go into 'old mode'
which keeps this nodejs process alive even after calling .off('keypress')
WORKAROUND: piping stdin via a transform stream allows us to call stream.destroy()
which then allows this nodejs process to close cleanly
* hotkeys integration
* implement Logger bottom float
* use registerGlobalBottomFloat for floating hotkeys instructions
* move registerGlobalBottomFloat calls into hotkeys implementation
* add test steps for unregistered hotkeys
+ update mock to return unregisterHotKeys mock
* fix lints
* setIsTTY(true) in tests
* add docs link to comment
* unregisterHotKeys before devEnv.teardown
* enable modifier key detection in hotkeys api
* fix: store previousBottomFloatLineCount in case the line count changes
+ ensures no existing logs (from before registerGlobalBottomFloat was called) are cleared
* fix: usages of console.dir/table -> logger.dir/table
+ use static methods of miniflare Log which are now stateful -- rather than reimplement in Wrangler's Logger not sharing state
* mark methods with unsafe_
* fixup
* use setIsTTY inside beforeEach
* use readline.moveCursor(stdout,...) instead of stdout.moveCursor(...)
* abstract knowledge of bototm float from logger implementations
* fix lints
* use readline.clearScreenDown
* handle forceLocal (disabled hotkey options)
* refactor
* update changeset type to refactor
* implement logger.console
* unregister hotkeys during auth prompt
* update AbortError checks
* fix logger.console types
* change getAccountId to requireAuth
* check isTTY in unregister keypress
* fix RemoteRuntimeController shutdown log
* use isNonInteractiveOrCI util
* hookify the hotkeys disabled option
* use isInteractive() instead of !isNonIteractiveOrCI()
This is the first of a few expected patches that normalize dependency versions, This normalizes `undici`, `concurrently`, `@types/node`, `react`, `react-dom`, `@types/react`, `@types/react-dom`, `eslint`, `typescript`. There are no functional code changes (but there are a couple of typecheck fixes).
* Implement additional E2E tests for `wrangler dev (--remote)`
* Rebase + rework e2e to use readUntil
* Kill Wrangler
* Use prebuilt node-pty to speedup CI installation
---------
Co-authored-by: Samuel Macleod <smacleod@cloudflare.com>
* ci: remove fixture from changeset releases
* ci: ensure that fixtures are not deployable
* ci: actually run the deploy script not the deploy command for deploying Workers and Pages
* fixup! ci: ensure that fixtures are not deployable
* Changing devCommand and deployCommand to string. Fixing next dev command
* Update TemplateConfig docs and remote unused field
* Remove shell-quote
* changeset
* Renaming devCommand to devScript. Responding to PR feedback
* Skip yarn + remix e2e tests
* fix: ensure `wrangler dev` exits with code `0` on clean exit
We were previously calling `process.disconnect()` twice: once in `dev`
specific code, and once in the CLI `main()` function. The 2nd call was
throwing with an already disconnected error causing `wrangler dev` to
exit with code `1`. This exception was being swallowed as `cli.ts`'s
`catch()` assumes the error has already been logged.
This change makes sure we only call `process.disconnect()` once, and
also logs errors in this `finally` block.
* fix: ensure `wrangler pages dev` exits cleanly
This change ensures the `onReady` function passed as a prop to
`InteractiveDevSession` is called when the hostname/port match the
initial values (the case for `wrangler pages dev` without flags).
This prevented the `Promise` returned by `unstable_dev()` in non-test
mode from resolving. This in turn prevented Pages' cleanup callbacks
being registered and `run pages dev` metrics being sent.
* test: add tests for interactive dev sessions and clean exits
This adds a new fixture test that runs `wrangler (pages) dev` in a
pseudo-TTY to test `InteractiveDevSession`. This allows us to test
`CTRL+C`/`x` clean exits without zombie `workerd` processes.