Remove tap, replace with vitest

[pvdz]

Remove tap, replace it with vitest.

Updated tests accordingly.

Inline snapshots here we come!

[jdalton]

Reduces the bug workarounds for tap 🎉 ! Let's see how discussions shake out over the next week!

[jdalton]

Okay. Let's do this.

[socket-security]

New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@vitest/coverage-v8@3.0.7	Transitive: environment, filesystem, shell	+53	7.84 MB	antfu, oreanno, patak, ...1 more
npm/vitest@3.0.7	Transitive: environment, filesystem, network, shell, unsafe	+66	260 MB

🚮 Removed packages: npm/@tapjs/run@4.0.2, npm/custompatch@1.1.4

View full report↗︎

Have feedback? Participate in our User Experience Survey 📊

[socket-security-staging]

New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@vitest/coverage-v8@3.0.7	Transitive: environment, filesystem, shell	+53	7.83 MB	vitestbot
npm/vitest@3.0.7	environment, eval Transitive: filesystem, network, shell, unsafe	+66	265 MB	vitestbot

🚮 Removed packages: npm/@tapjs/run@4.0.2, npm/custompatch@1.1.4

View full report↗︎

[jdalton]

AbortController is built-in to Node. It's also a browser standard. Node and its APIs accept the signal

const controller = new AbortController();
const signal = controller.signal;

as a way to abort requests or operations.

The registry and CLI share an abortSignal that is wired through things that will abort when 'signal-exit' fires its onExit callback. This works for things like Ctrl^C and other stuff making for clean CLI exits.

We should run Vitest without JSDOM if possible.

[jdalton]

No longer need to add this as it's added before.

[pvdz]

So the TAP one is redundant too?

[pvdz]

gonna merge. if redundant we can drop it in a separate PR. it doesnt seem to block right now