practica
node-starter-kit
practica | node-starter-kit | |
---|---|---|
5 | 13 | |
1,333 | 155 | |
1.5% | 5.2% | |
6.0 | 1.8 | |
19 days ago | almost 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
node-starter-kit
- Good Examples of Testing in an Open Source Repo?
- Ask HN: Who wants to be hired? (June 2021)
-
Preparing a project, and a tehnologies stack
Here is link number 1 - Previous text "API"
-
How do you deploy your NodeJS APIs?
I'm deploying by either manually by running yarn deploy script or firing it via GitHub Actions when a PR is created, updated, or merged to the main branch.
- Node or serverless for my app?
-
Minimal Node.js boilerplate with Prettier and ESlint
Example: github.com/kriasoft/node-starter-kit
-
Any Laravel Eloquent like ORM for node.js?
Nope. Just plain GraphQL.js + Knex.js (example), often typed manually since it's not where most of the time spend on when building an API server (though it can be automated via a scaffolding script if there are too many db tables). Generating TypeScript definitions off the actual db schema using knex-types (example).
-
What is new with node.js world?
Examples: - https://github.com/kriasoft/node-starter-kit - basic Node.js API starter kit - https://github.com/kriasoft/graphql-starter - monorepo template with GraphQL, React, Relay
-
Ask HN: Who wants to be hired? (May 2021)
I can help you developing a (GraphQL API) server for your web and/or mobile app as well as CI/CD workflows, optimized for serverless infrastructure in Google Cloud Platform. The initial version (first iteration) will be ready and live in under three days! Code examples:
https://github.com/kriasoft/node-starter-kit
-
NodeJs Best practices
You may want to browse through https://github.com/kriasoft/node-starter-kit to pick up some common patterns (e.g. transactional emails, OAuth 2.0 authentication, user sessions, views, db migrations, etc.).
What are some alternatives?
bulletproof-nodejs - Implementation of a bulletproof node.js API 🛡️
nestjs-bff - A full-stack TypeScript solution, and starter project. Includes an API, CLI, and example client webapp. Features include production grade logging, authorization, authentication, MongoDB migrations, and end-to-end testing.
startify - Deployable monorepo boilerplate powered by fastify (node.js) and React. Ideal for rapid prototyping and going to production as fast as possible.
express-typescript-boilerplate - A delightful way to building a RESTful API with NodeJs & TypeScript by @w3tecch
fastify-jumpstart - Template for a database agnostic fastify typescript web API including local JWT auth, OAS3, and testing.
cloudbeaver - Cloud Database Manager
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]
react-native-typescript-boilerplate - React Native Typescript starter kit / template (Redux Thunk + React Native Navigation v7)
fastify-typescript-generator - generates new fastify applications in everyone's favourite language typescript with various options to choose from based on your project needs
starter-reactjs-nestjs-mysql - Starter React.js NestJS MySQL with continuous integration and AWS deployment
Angular-Full-Stack - Angular Full Stack project built using Angular, Express, Mongoose and Node. Whole stack in TypeScript.
tinyws - 🚡 tiny WebSocket middleware for Node.js