neon-testing 1.0.0 → 1.0.1

package/README.md

@@ -1,10 +1,14 @@
 # Neon testing
 
-A Vitest utility for running database tests with isolated [Neon](https://neon.com/) branches. Each test file gets its own dedicated PostgreSQL database (Neon branch), ensuring clean, parallel, and reproducible tests.
+A Vitest utility for automated integration tests with [Neon](https://neon.com/).
+
+Each test file runs against its own isolated PostgreSQL database (Neon branch), ensuring clean, parallel, and reproducible testing of code that relies on a database. Because it uses a real database, you can test code logic that depends on database features such as transaction rollbacks, unique constraints, and more.
+
+Using an actual clone of your production database for integration testing lets you verify functionality that mocks cannot.
 
 ## Features
 
-- 🔄 **Isolated test environments** - Each test file runs against its own Neon branch
+- 🔄 **Isolated test environments** - Each test file runs against its own Postgres database with your actual schema and constraints
 - 🧹 **Automatic cleanup** - Neon test branches are created and destroyed automatically
 - 🛡️ **TypeScript native** - No JavaScript support
 - 🎯 **ESM only** - No CommonJS support
@@ -124,22 +128,18 @@ Tests within a single test file share the same database instance (Neon branch),
 
 This works because Vitest runs test files in parallel, but tests within each test file run one at a time.
 
-## License
-
-This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
-
 ## Contributing
 
 Contributions are welcome! Please open issues or pull requests on [GitHub](https://github.com/starmode-base/neon-testing/pulls).
 
-## Support
+## License
 
-For questions or support, open an issue on [GitHub](https://github.com/starmode-base/neon-testing/issues).
+This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
 
-## Commercial support
+## Need expert help?
 
-Need professional help with database testing, AI integration, or modern web development?
+I take on a few consulting projects each year where I can build, unblock, and ship.
 
-**[STΛR MODΞ](https://www.starmode.dev/)** - I run this AI development studio with data scientist and ML/AI expert Spencer Smith. We specialize in building AI-first applications, advanced AI workflows, and agentic networks. We help companies build reliable AI solutions.
+**[STΛR MODΞ](https://www.starmode.dev/)** — The AI development studio I run with AI/ML expert and data scientist Spencer Smith. We help companies build accurate AI solutions: AI-first apps, advanced workflows, and agentic systems.
 
-**[Mikael Lirbank](https://www.lirbank.com/)** - My individual consulting practice for web application development, test automation, code quality, and technical architecture.
+**[Mikael Lirbank](https://www.lirbank.com/)** — My solo practice, focused on web app development, test automation, code quality, and technical architecture. I'm around, friendly, and happy to help with the hard stuff.

package/index.ts

@@ -140,8 +140,6 @@ export function makeNeonTesting(factoryOptions: NeonTestingOptions) {
     afterAll(async () => {
       await deleteBranch();
       process.env.DATABASE_URL = undefined;
-
-      // await deleteAllTestBranches();
     });
   };
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "neon-testing",
-  "version": "1.0.0",
-  "description": "A Vitest utility for running database tests with isolated Neon branches",
+  "version": "1.0.1",
+  "description": "A Vitest utility for automated integration tests with Neon",
   "keywords": [
     "neon",
     "postgres",
@@ -25,8 +25,8 @@
     "@neondatabase/api-client": "^2.0.0"
   },
   "peerDependencies": {
-    "typescript": "^5",
-    "vitest": "^3"
+    "typescript": "^5.8.3",
+    "vitest": "^3.2.2"
   },
   "devDependencies": {
     "@neondatabase/serverless": "^1.0.1",