I am going to have to spend some time comparing this with https://koajs.com/
I still haven’t seen Koa out in the wild and I like the sound of TypeScript being used here... the FAQ says it’s not compatible with Sails which I would consider a Good Thing(tm).
Past the point of editing- but if y'all feel like downvoting me out of disagreement perhaps you could take the time to comment with an opposing opinion?
A spool-koa could be a potential spool in the fabrix ecosystem. Fabrix builds on top of other node web frameworks using a plugin system called spools. Currently you could either use spool-express or spool-hapi in your fabrix app.
I saw that it had the other spool repos but I got my hot takes from the info on https://github.com/fabrix-app/fabrix and it didn’t really click that a Koa spool would be one of the options — thanks for taking the time to point that out.
This seems...fine, in that I guess it's better that this is out there than not, but:
- Nest.js already kills in this role and I'm not seeing a lot of justification for "use this instead." That team, too, has a really impressive set of integrations and their stuff does a really good job of playing nice with each other.
- Sequelize over TypeORM when you're using TypeScript is a bold (read: IMO, foolish) decision. TypeORM is the least awful ORM I've seen in any language other than Ruby and Sequelize wasn't very good for JavaScript; it's all kinds of clunky for TypeScript.
- Is manual routing, instead of something like attribute discovery, really what people want these days when they're using a convention-over-configuration framework? Rails had to do it; NodeJS frameworks have other alternatives.
Anybody who's used this have any thoughts on why one would go with it over Nest.js or Koa?
12 comments
[ 3.6 ms ] story [ 36.9 ms ] threadI am going to have to spend some time comparing this with https://koajs.com/
I still haven’t seen Koa out in the wild and I like the sound of TypeScript being used here... the FAQ says it’s not compatible with Sails which I would consider a Good Thing(tm).
I saw that it had the other spool repos but I got my hot takes from the info on https://github.com/fabrix-app/fabrix and it didn’t really click that a Koa spool would be one of the options — thanks for taking the time to point that out.
Also using TypeScript. They go great together.
- Nest.js already kills in this role and I'm not seeing a lot of justification for "use this instead." That team, too, has a really impressive set of integrations and their stuff does a really good job of playing nice with each other.
- Sequelize over TypeORM when you're using TypeScript is a bold (read: IMO, foolish) decision. TypeORM is the least awful ORM I've seen in any language other than Ruby and Sequelize wasn't very good for JavaScript; it's all kinds of clunky for TypeScript.
- Is manual routing, instead of something like attribute discovery, really what people want these days when they're using a convention-over-configuration framework? Rails had to do it; NodeJS frameworks have other alternatives.
Anybody who's used this have any thoughts on why one would go with it over Nest.js or Koa?
Agreed wrt sequelize, mind, every time I look at it I want to port my perl sql interface code to replace it.
I'll look at TypeORM though, thanks.