Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Stator: A full-stack boilerplate – releases, deployments, enforced conventions

github.com

Post reply on HN
Print view View original

21–30 of 34 posts

Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions

#21

Post by yann510 »

beders wrote: post #13

How long will this be good for? Has the pace of library turn-over slowed over in JS land? Last time I checked, express was still a thing for web services.

We've currently selected very hot and trendy libraries which are currently maintained. Although the goal of this project is to be used for projects in production. Right now we haven't tested anything large scale, but the goal would be to replace any technology that isn't suitable for production.

We will be testing stator out with a large scale production project (that's why we plan on implementing kubernetes support) and we will update the libraries accordingly.

Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions

#23

Post by beeman »

vekker wrote: post #22

It's funny how the author went for React for the frontend, even though Angular + Nest.js are a much more synergistic duo. He even structured the application like a typical Angular app.... Why not simply just go with Angular? :D

I'm working on a set of schematics that generate an Nx Workspace using NestJS and Angular. It uses GraphQL to communicate between frontend and backend and the data layer uses Prisma.

It's pretty much work in progress but you should be able to scaffold out a new working project.

Feel free to check it out. Happy to answer any questions

https://github.com/nxpm/stack

Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions

#24

Post by nikolasburk »

yann510 wrote: post #20
nahtnam wrote: post #15

Earlier quoted context omitted.

Check out Prisma. It generates lot more complex types and supports relationships pretty well

I will definitely check this out, thanks for sharing!

Nikolas from the Prisma team here :) let me know if you have any questions, always happy to help! (You can ping me on the Prisma Slack [1], I'm `@nikolasburk` there as well).

Also note that we've just opened up an early access program for Prisma Migrate [2] (which enables schema and data migrations), would love to hear your thoughts on our approach!

[1] https://slack.prisma.io

[2] https://www.notion.so/prismaio/Public-Documentation-for-Pris...

Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions

#25

Post by whofw »

nahtnam wrote: post #15
whofw wrote: post #10

Curious 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

I've been really interested in checking out Primsa, but I was a little concerned about putting an extra layer between the database and the app. I should give it another look.

Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions

#26

Post by dkarp »

vekker wrote: post #22

It's funny how the author went for React for the frontend, even though Angular + Nest.js are a much more synergistic duo. He even structured the application like a typical Angular app.... Why not simply just go with Angular? :D

maybe they were familiar with React and not with Angular?

Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions

#27

Post by yann510 »

vekker wrote: post #22

It's funny how the author went for React for the frontend, even though Angular + Nest.js are a much more synergistic duo. He even structured the application like a typical Angular app.... Why not simply just go with Angular? :D

Totally biased opinion as I'm familiar with React, but if you want to learn more about the thought process behind the decision, I recommend reading this: https://yann510.hashnode.dev/creating-a-todo-application-usi...

Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions

#28

Post by yann510 »

beeman wrote: post #23
vekker wrote: post #22

It's funny how the author went for React for the frontend, even though Angular + Nest.js are a much more synergistic duo. He even structured the application like a typical Angular app.... Why not simply just go with Angular? :D

I'm working on a set of schematics that generate an Nx Workspace using NestJS and Angular. It uses GraphQL to communicate between frontend and backend and the data layer uses Prisma. It's pretty much work in progress but you should be able to scaffold out a new working project. Feel free to check it out. Happy to answer any questions https://github.com/nxpm/stack

Very interesting, we should get in touch to see if there is a possibility of collaboration here. If interested, email me y.thibodeau1@gmail.com

Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions

#29

Post by yann510 »

nikolasburk wrote: post #24
yann510 wrote: post #20

Earlier quoted context omitted.

I will definitely check this out, thanks for sharing!

Nikolas from the Prisma team here :) let me know if you have any questions, always happy to help! (You can ping me on the Prisma Slack [1], I'm `@nikolasburk` there as well). Also note that we've just opened up an early access program for Prisma Migrate [2] (which enables schema and data migrations), would love to hear your thoughts on our approach! [1] https://slack.prisma.io [2] https://www.notion.so/prismaio/Publi…

Awesome, will definitely check that out!

Re: Stator: A full-stack boilerplate – releases, deployments, enforced conventions

#30

Post by nightowl_games »

People in the web world frequently omit identifying their technology as being in the web world. For people outside the web world, like me, it's tedious to scan for key identifiers amongst the generic terminolgy like "template" and "application".
Post reply on HN