practica
nodebestpractices
practica | nodebestpractices | |
---|---|---|
5 | 73 | |
1,333 | 96,436 | |
1.5% | - | |
6.0 | 7.6 | |
19 days ago | 13 days ago | |
TypeScript | Dockerfile | |
MIT License | Creative Commons Attribution Share Alike 4.0 |
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
nodebestpractices
-
10 GitHub Repos for Mastering JavaScript
Repository: goldbergyoni/nodebestpractices
- 18 Must-Bookmark GitHub Repositories Every Developer Should Know
-
ReactJS, NextJS and the modern frontend community (Rant)
ah, but there is one more reason to return await. have a read.
-
10 GitHub Repos to Become a Better Backend Developer
View on GitHub
- Node.js Best Practices
-
Fastify Typescript Boilerplate with Redis and RabbitMQ
Flat structure: check out the structure recommended by node best practices, and check out how Nest.js does the structure. The more layers you add, the more complex navigation with the flat structure becomes. With the component structure, it stays easy to use no matter how many components and layers you have.
-
sql best practices
I am looking for a resource like https://github.com/goldbergyoni/nodebestpractices. I know Sql but I want to learn best practices. Can you recommend me resources for this?
-
Difference between services and middleware
Also, while learning nodejs + express, have a read on the best practices here.
-
Searching for NodeJS Interview preparation material
Assuming you have fundamentals in place this repo of best practices can help line things up and link you to areas where you need improvement. https://github.com/goldbergyoni/nodebestpractices
-
I admit it - I don't really understand what's going on with Node.js with regard to "single threadedness". Please help me understand.
Please don't call node.js single-threaded as this is not true and is annoying. To take advantage of CPUs, this could help.
What are some alternatives?
bulletproof-nodejs - Implementation of a bulletproof node.js API 🛡️
numjs - Like NumPy, in JavaScript
startify - Deployable monorepo boilerplate powered by fastify (node.js) and React. Ideal for rapid prototyping and going to production as fast as possible.
parquetjs - fully asynchronous, pure JavaScript implementation of the Parquet file format
node-starter-kit - Node.js / GraphQL project template pre-configured with TypeScript, PostgreSQL, login flow, transactional emails, unit tests, CI/CD workflow.
domain-driven-hexagon - Learn Domain-Driven Design, software architecture, design patterns, best practices. Code examples included
fastify-jumpstart - Template for a database agnostic fastify typescript web API including local JWT auth, OAS3, and testing.
jest-image-snapshot - ✨ Jest matcher for image comparisons. Most commonly used for visual regression testing.
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]
oas-tools - NodeJS module to manage RESTful APIs defined with OpenAPI 3.0 Specs over express servers.
fastify-typescript-generator - generates new fastify applications in everyone's favourite language typescript with various options to choose from based on your project needs
clean-code-javascript - :bathtub: Clean Code concepts adapted for JavaScript