practica
relay-starter-kit
practica | relay-starter-kit | |
---|---|---|
5 | 9 | |
1,333 | 3,820 | |
1.5% | - | |
6.0 | 7.1 | |
18 days ago | 4 months 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
relay-starter-kit
-
Is NEXT.JS really that helpful versus react + express?
https://github.com/kriasoft/react-starter-kit (or, relay-starter-kit)
- Ask HN: Who wants to be hired? (June 2022)
-
Best Ways to Make an Ecommerce Store on Node.js in 2022 | Guide for Beginners
GitHub
-
What is the consensus about using ORM in node js applications?
It also helps to have a REPL shell for Knex.js β https://i.imgur.com/P5bVdoC.gif
-
graphql-code-generator - how do I generate enums from TypeScript enums?
I generate TypeScript enums and types from the actual database schema using knex-types as part of the yarn db:reset script that used during local development (after making changes to the db schema migration files). See example project.
-
π°π¦Έ Production-ready template for backends created with Node.js, Typescript and Express
I tried to take advantage of TypeORM in a couple of projects, but then reverted back to knex + knex-types β just a PostgreSQL client with query builder works great, IMO, especially for GraphQL API development.
-
Caching in GraphQL
GraphQL API and Relay Starter Kitβ an example of implementing GraphQL API optimized for the serverless environment (Google Cloud Functions) + a reverse proxy using Cloudflare Workers
-
Looking for know how on managing Cron Jobs
It helps to have a monorepo setup with packages/projects such as "api", "worker" (cron job) etc. all consuming the same environment variables (db connection settings etc.), when the cron job "serverless" function is deployed, it just picks the required environment variables from the shared "env" folder/package.
- GraphQL API and Relay Starter Kit
What are some alternatives?
bulletproof-nodejs - Implementation of a bulletproof node.js API π‘οΈ
hono - Web Framework built on Web Standards
startify - Deployable monorepo boilerplate powered by fastify (node.js) and React. Ideal for rapid prototyping and going to production as fast as possible.
miniflare - π₯ Fully-local simulator for Cloudflare Workers. For the latest version, see https://github.com/cloudflare/workers-sdk/tree/main/packages/miniflare.
node-starter-kit - Node.js / GraphQL project template pre-configured with TypeScript, PostgreSQL, login flow, transactional emails, unit tests, CI/CD workflow.
nestjs-prisma-monorepo - π NestJS + Prisma + Yarn Workspaces (Monorepo) full-stack project template
fastify-jumpstart - Template for a database agnostic fastify typescript web API including local JWT auth, OAS3, and testing.
mantine-next-template - Mantine + Next.js pages router template [Moved to: https://github.com/mantinedev/next-pages-template]
graphql-starter-kit - π₯ Yarn v2 based monorepo template (seed project) pre-configured with GraphQL API, PostgreSQL, React, Relay, and Material UI. [Moved to: https://github.com/kriasoft/graphql-starter]
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
fastify-typescript-generator - generates new fastify applications in everyone's favourite language typescript with various options to choose from based on your project needs
SkyOffice - Immersive virtual office built with Phaser, React, Redux, PeerJS, and Colyseus.