practica
graphql-starter-kit
practica | graphql-starter-kit | |
---|---|---|
5 | 2 | |
1,333 | 3,190 | |
1.5% | - | |
6.0 | 7.6 | |
19 days ago | about 3 years ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
practica
-
10 GitHub Repos to Become a Better Backend Developer
🔖 Curious to see examples? We have a starter: Visit Practica.js, our application example and boilerplate (beta) to see some practices in action
-
Transitioning from SpringBoot to node and not sure where to learn
Good practices to me means being disciplined with good coding standards regardless of framework you'd work in. I've seen terrible codes in Spring, .NET just as I would see in any node.js project. Does framework like Spring enforce structure that your team could possibly have some guidelines to follow? Sure it does. Does spring make your team stick with best practices? I don't know about that. For example, using interface for places where you need (or at least java bean managed modules) is key to achieving good modularization in Spring, it's the same in Javascript. However, due to the nature of its language features, fewer places require using actual interface in Javascript. The underlying principles are not much different, it's just different ways of achieving the goal. That said, shooting yourself in the foot in express will give you much deeper learning experience than using something like nest to make you feel comfortable. At one point, I am sure you'd get hang of good and bad of Javascript. Meanwhile, you could use something like https://practica.dev/ as a reference to explore some of good/bad practices and build upon it.
-
3 layer architecture nodejs examples in the wild? (repos/open source?)
I found an interesting repo that seems to answer my questions and more. If a future developer stumbles across this thread, check it out here: https://github.com/practicajs/practica
-
Why would one keep controller small?
If you don't mind, take a look at following example: https://github.com/practicajs/practica/tree/main/src/code-templates/services/order-service/entry-points/api
-
Node Masterpieces
Have a look at practica.js
graphql-starter-kit
What are some alternatives?
bulletproof-nodejs - Implementation of a bulletproof node.js API 🛡️
express-typescript-boilerplate - A delightful way to building a RESTful API with NodeJs & TypeScript by @w3tecch
startify - Deployable monorepo boilerplate powered by fastify (node.js) and React. Ideal for rapid prototyping and going to production as fast as possible.
GETProtocolCoreV1.0-DEPRECIATED - 🎫 Contract overview and definition of GET Protocol's NFTs
node-starter-kit - Node.js / GraphQL project template pre-configured with TypeScript, PostgreSQL, login flow, transactional emails, unit tests, CI/CD workflow.
hono - Web Framework built on Web Standards
fastify-jumpstart - Template for a database agnostic fastify typescript web API including local JWT auth, OAS3, and testing.
blockfrost-js - Node.js SDK for the Blockfrost.io API.
fastify-typescript-generator - generates new fastify applications in everyone's favourite language typescript with various options to choose from based on your project needs
notion-cloudflare-worker - A Github Action CI wrapper for Fruition setup for automatic deployment to CloudFlare Worker, to help you use your Notion with custom domain
Angular-Full-Stack - Angular Full Stack project built using Angular, Express, Mongoose and Node. Whole stack in TypeScript.
react-starter-kit - The web's most popular Jamstack front-end template (boilerplate) for building web applications with React