pg-nano

o-reconnect with exponential backoff, and query streaming on top of libpq. It scans a directory for `.sql` files and instantly updates your local database instance by diffing the current schema with the desired schema. It only drops data if absolutely necessary. Note that I haven't implemented production migrations yet, which will of course err on the safe side. I use a combination of static analysis (parsing your SQL) and introspection (querying Postgres system tables) at compile time to both generate the TypeScript bindings and the migration plan. The link again: https://github.com/pg-nano/pg-nano/ ~~~ I posted all this to get your feedback: - Could you see yourself using pg-nano? Why or why not? - Are there specific features you’d like to see, or concerns you have? I could really use some beta testers, but even your thoughts would help a great deal. ~~~ In order to get pg-nano production ready, I have a few things left to do. 1. Database seeding 2. Migrations in production 3. Transactions

etadata for RPC-style API routing. I could not find a library that simplifies the task of writing a code generator, so I made jumpgen. # What It Does It's designed to handle the burdens of implementing a “watch mode” for your generators. It also returns an event emitter, especially useful for logging. Your generator is free to work in relative paths, since jumpgen handles path resolution according to a user-provided root directory. It tracks which files your generator has read into memory and which directories your generator has listed. When those files/directories are changed or have files added/removed, your generator will rerun automatically (if watch mode is enabled). This even works with globs! I've also included a "dedent" helper function so you can indent any template literal without that excess indentation carrying over into the emitted files. # Feedback Wanted If this sounds interesting to you, I'd love to hear any comments or criticisms about the API, the readme, or whatever else. Thanks! [1]: https://github.com/pg-nano/pg-nano

o my surprise, I discovered that libpg_query, the C library used under-the-hood, includes JSON definitions in their /srcdata/ folder. I figured I could use them to generate the type definitions. Genius, right? Okay... maybe not genius, but still cool, I think. You see, those JSON definitions provided by libpg_query? They don't exactly contain the TypeScript definitions (was that obvious?). No, no. I had to translate them into TypeScript definitions. (I'm sure you could have done it, yes yes. But did you? No siree bob) It was pain-staking, but overall really not too hard. Time-consuming? Yes, but not as much as writing the type definitions by hand. So... was it worth it? Only time will tell. I hope you find it as useful as I do. And that's all I've got, so thanks for reading. P.S. The build for Windows is broken, so if anyone could lend a hand, you would be a true hero. [1]: https://github.com/pg-nano/pg-nano (not ready for production use)