Postgres.js VS Nodewood

I want to use this as a chance to bring attention to a GitHub issue that I think would help reduce friction for Neon: https://github.com/neondatabase/neon/issues/4989. Having run a local dev environment connected to Neon and tests connected to Neon got in our way of adoption. We'd prefer to develop and run tests against a regular Postgres localhost database. To the PMs of Neon, put yourself in the shoes of a new... - Source: Hacker News / 21 days ago

I'd push you to consider using postgres, slonik or similar for database queries. With these libraries, you just write SQL, but they perform input sanitization for you. So you can safely write:. Source: 5 months ago

There's also https://kysely.dev/ but personally I handwrite my queries with https://github.com/porsager/postgres for flexibility and performance most orms use node-pg lib which has shit performance. - Source: Hacker News / 7 months ago

When viewed as a DSL for set theory, views, CTEs, set-returning functions, et al are indeed proper first-class query abstractions. When viewed through the lens of general purpose imperative or functional programming languages, it's easy to see how it can be seen as falling short. I'll admit much of the tooling and driver APIs leave a lot to be desired. Some tools do make good efforts though such as nested... - Source: Hacker News / 8 months ago

Demonstrate how easily and accidentally one can make an SQL injection with these: https://github.com/porsager/postgres. - Source: Hacker News / 10 months ago

Hey, thanks for the mention! I'm the creator of Nodewood, and I'm happy to answer any questions anyone has on it, or really anything else in the space I can help with. Source: about 1 year ago

This is largely why I built Nodewood [1]. Every time I wanted to start a new project, almost always a SaaS idea, I'd skip over the "boring stuff" like building user management, subscription management, teams, admin, all that, to get to the meat of the business logic, to make sure I had a valid idea. But I still needed all that stuff eventually, so I'd have to lose time later building it all in! So I decided to... - Source: Hacker News / almost 2 years ago

This is actually part of why I created Nodewood [1], because every new Node project required pulling all that together, and every new SaaS idea I had had the same basic requirements (user management, subscription management, teams support, etc). Then I figured, if I found this useful, surely others would too, so I packaged it up and have had a few happy customers since then, who have helped me refine it, which... - Source: Hacker News / almost 2 years ago

Well, I've spoken about this before, and on here no less, but only really in response to posts like this. I don't do any advertising or speak about mine except in interviews, since it's usually indicative of the kind of requirements they're looking for. I created a SaaS bootstrap for Javascript called Nodewood [1]. It actually started as just a template for me, because there's a lot of setup for each new JS web... - Source: Hacker News / almost 2 years ago

Disclaimer: I'm the author of the following boilerplate. Nodewood (https://nodewood.com/) is a Javascript SaaS boilerplate built to take advantage of using Javascript on the server and in the UI. Models, Validators, and other business logic can be re-used in both builds, so you don't have to write, rewrite, and maintain that logic in both places, or in different languages. It has built-in subscription management... - Source: Hacker News / about 2 years ago