Stator: A full-stack boilerplate – releases, deployments, enforced conventions
1–10 of 34 posts
Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions
#2Am a data scientist and don’t do anything with JavaScript but I love seeing stuff like this just to get a feel for the lay of the land and how everything fits together.
Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions
#3Am a data scientist and don’t do anything with JavaScript but I love seeing stuff like this just to get a feel for the lay of the land and how everything fits together.
Happy you like the stack :)
Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions
#4Very cool. Node has been on my back burner to learn for years, but making the mental leap from tutorial-sized projects to anything more complex has been particularly difficult. Perhaps this will help!
Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions
#5Very cool. Node has been on my back burner to learn for years, but making the mental leap from tutorial-sized projects to anything more complex has been particularly difficult. Perhaps this will help!
Yeah this handles a lot of the complexity of setting up a complete project with TypeScript and has some nice examples. Try it out and let me know how it went ;)
Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions
#6Why fastify and nest?
Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions
#7Why fastify and nest?
You can read this article to get all the details on the decision: https://yann510.hashnode.dev/the-best-node-web-framework-par...
Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions
#8Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions
#9Cool 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.
Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions
#10Curious 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 there, especially when you compare them to more mature projects like Rails' ActiveRecord or Laravel's Eloquent.