Release v3.0.0 · starmode-base/neon-testing · GitHub
//releases/show" data-turbo-transient="true" />
Skip to content
Search or jump to...
Search code, repositories, users, issues, pull requests...
-->
Search
Clear
Search syntax tips
Provide feedback
--><br>We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Cancel
Submit feedback
Saved searches
Use saved searches to filter your results more quickly
-->
Name
Query
To see all available qualifiers, see our documentation.
Cancel
Create saved search
Sign in
//releases/show;ref_cta:Sign up;ref_loc:header logged out"}"<br>Sign up
Appearance settings
Resetting focus
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
starmode-base
neon-testing
Public
Notifications<br>You must be signed in to change notification settings
Fork
Star<br>21
v3.0.0
Latest
Latest
Compare
Choose a tag to compare
Sorry, something went wrong.
Filter
Loading
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
No results found
View all tags
github-actions
released this
17 Jun 17:34
v3.0.0
c47c81b
v3.0.0 makes Neon Testing runner-aware, with explicit entry points for Vitest, Bun Test, shared utilities, setup, and custom runners.
What's new
Added first-class Bun Test support via neon-testing/bun.
Added explicit entry points:
neon-testing/vitest
neon-testing/bun
neon-testing/core
neon-testing/setup
neon-testing/utils
Added runner-registered DATABASE_URL safeguarding through neon-testing/setup, replacing the Vitest/Vite plugin.
Added runner-agnostic core support for custom test runners by passing lifecycle hooks manually.
Expanded coverage across Vitest and Bun, including Neon serverless, pg, Postgres.js, Drizzle, pooled and direct connections, HTTP, TCP, and WebSocket usage.
Breaking changes
The root import has been removed. Use the Vitest entry point instead:
// v2<br>import { makeNeonTesting } from "neon-testing";
// v3<br>import { makeNeonTesting } from "neon-testing/vitest";
The Vite plugin entry point has been removed. Register neon-testing/setup directly with your test runner.
neon-testing/utils no longer re-exports the deprecated Vite plugin helper. lazySingleton and createBarrier remain available.
Type names changed: factory options are now MakeNeonTestingOptions, and per-file overrides are now NeonTestingOptions.
The minimum Node.js version is now >=22.
Upgrading from v2
Most Vitest projects need three changes:
Change imports from neon-testing to neon-testing/vitest.
Remove the old Vite plugin usage, if present.
Add neon-testing/setup to Vitest setupFiles.
// vitest.config.ts<br>import { defineConfig } from "vitest/config";
export default defineConfig({<br>test: {<br>setupFiles: ["neon-testing/setup"],<br>},<br>});
Full Changelog : v2.7.0...v3.0.0
Assets
Loading
Uh oh!
There was an error while loading. Please reload this page.
-->
All reactions
You can’t perform that action at this time.