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 2 years 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 3 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 3 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 3 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 3 years ago

There is also no requirement to follow the PHP-FIG standards. The best thing that is build because of those standards is Composer. The most plugins I downloaded while writing use composer. The problem is that the plugins ship with their own vendor directory. While the standard is to have one vendor directory for the whole project. This results in different packages with the same or different version of it in the... - Source: dev.to / about 1 month ago

“Extensions are now very close to being like packages; they basically look like Composer packages. It’s still open to discussion whether PIE will be part of Composer someday. It’s not decided yet, but I hope it will be,” Roman added. - Source: dev.to / about 1 month ago

Dependencies are managed by Composer (like npm, cargo, etc) for more than 10 years now. https://getcomposer.org. - Source: Hacker News / about 1 month ago

Composer and Packagist have become key tools for establishing the foundations of PHP-based applications. Packagist is essentially a directory containing PHP code out of which Composer, a PHP-dependency manager, retrieves packages. Their ease of use and exceptional features simplify the process of importing and managing own and third-party components into our PHP projects. - Source: dev.to / 3 months ago

Simplicity: Getting started is a breeze—install via Composer, define some routes, and you’re off. Scaling up? Add middleware or libs like Twig or Eloquent as needed. - Source: dev.to / 3 months ago