Cool project! I like the building block approach. Is optional graphQL support on your mind? I have seen working examples using typeorm models and some glue code/libraries.
Stator: A full-stack boilerplate – releases, deployments, enforced conventions
11–20 of 34 posts
Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions
#12Curious about your thoughts on TypeORM. Have you used it at scale at all? I rebuilt the API portion of an app using it a few months ago and instantly ran into issues with things like relationships and slightly more complex queries. I know it is an ORM and isn't suitable for every use case and definitely not super-complex queries, but it seemed very limited and unstable. Honestly, I don't like any of the Node ORMs out…
Even with these encountered problems, I'm still willing to give it a try for my upcoming project. I'll probably write an article on this if things go bad.
For sure, this is less mature then the others out there, but I think it has a bright future as it has a nice syntax and cool features.
Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions
#13Last time I checked, express was still a thing for web services.
Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions
#14Curious about your thoughts on TypeORM. Have you used it at scale at all? I rebuilt the API portion of an app using it a few months ago and instantly ran into issues with things like relationships and slightly more complex queries. I know it is an ORM and isn't suitable for every use case and definitely not super-complex queries, but it seemed very limited and unstable. Honestly, I don't like any of the Node ORMs out…
Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions
#15Curious about your thoughts on TypeORM. Have you used it at scale at all? I rebuilt the API portion of an app using it a few months ago and instantly ran into issues with things like relationships and slightly more complex queries. I know it is an ORM and isn't suitable for every use case and definitely not super-complex queries, but it seemed very limited and unstable. Honestly, I don't like any of the Node ORMs out…
Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions
#16Curious about your thoughts on TypeORM. Have you used it at scale at all? I rebuilt the API portion of an app using it a few months ago and instantly ran into issues with things like relationships and slightly more complex queries. I know it is an ORM and isn't suitable for every use case and definitely not super-complex queries, but it seemed very limited and unstable. Honestly, I don't like any of the Node ORMs out…
I haven't used typeorm for any real world projet yet. Although when I tried using the mongo driver, literally nothing worked. I also ran into problems from the generated migrations where I would get errors when trying to run them. Even with these encountered problems, I'm still willing to give it a try for my upcoming project. I'll probably write an article on this if things go bad. For sure, this is less mature then…
Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions
#17Curious about your thoughts on TypeORM. Have you used it at scale at all? I rebuilt the API portion of an app using it a few months ago and instantly ran into issues with things like relationships and slightly more complex queries. I know it is an ORM and isn't suitable for every use case and definitely not super-complex queries, but it seemed very limited and unstable. Honestly, I don't like any of the Node ORMs out…
For my next project, I will check out Mikro-Orm.
Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions
#18Curious about your thoughts on TypeORM. Have you used it at scale at all? I rebuilt the API portion of an app using it a few months ago and instantly ran into issues with things like relationships and slightly more complex queries. I know it is an ORM and isn't suitable for every use case and definitely not super-complex queries, but it seemed very limited and unstable. Honestly, I don't like any of the Node ORMs out…
I've been using TypeOrm in production for a few years in a project with dozens of entity types and hundreds of queries. My recommendation is to use something else. Anyone know of an alternative?
Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions
#19Curious about your thoughts on TypeORM. Have you used it at scale at all? I rebuilt the API portion of an app using it a few months ago and instantly ran into issues with things like relationships and slightly more complex queries. I know it is an ORM and isn't suitable for every use case and definitely not super-complex queries, but it seemed very limited and unstable. Honestly, I don't like any of the Node ORMs out…
I cannot recommend it. It has a bug on sqlite that swaps the arguments randomly. This is super bad. For my next project, I will check out Mikro-Orm.
Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions
#20Curious about your thoughts on TypeORM. Have you used it at scale at all? I rebuilt the API portion of an app using it a few months ago and instantly ran into issues with things like relationships and slightly more complex queries. I know it is an ORM and isn't suitable for every use case and definitely not super-complex queries, but it seemed very limited and unstable. Honestly, I don't like any of the Node ORMs out…
Check out Prisma. It generates lot more complex types and supports relationships pretty well