food-app_be
orchid-orm-benchmarks
food-app_be | orchid-orm-benchmarks | |
---|---|---|
2 | 6 | |
1 | 12 | |
- | - | |
10.0 | 6.2 | |
over 1 year ago | 7 months ago | |
TypeScript | TypeScript | |
- | - |
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.
food-app_be
-
Rate my project made with Express + TS
Because I don't get it, I don't understand how to deal with certain situations. For example: In line 19 https://github.com/RicardoRien/food-app_be/blob/main/services/auth.service.ts
orchid-orm-benchmarks
-
How do you create test cases for APIs?
Here are my tests for an example project. The logic is quite straightforward: create db records, make a request, check the response, and if it was a mutating request check how it affected the database.
-
Examples of APIs that follows the best practices and are production ready on Github?
And if you like to see a random example project here is mine, but my point is that a random project won't really help because each project has a unique set of frameworks/libs/practices and it changes almost everything.
-
Announcing a new TypeScript ORM
Or you can clone this examples repo and play with the Blog API code.
-
Is there a good example of a real world NodeJS API project?
I have an example app, and have written documentation based on it, and I'd appreciate it if you could look and give some feedback. Yes, the doc is about ORM, but imagine the ORM is just an implementation detail and instead look at how validations, controllers, repos, and especially tests are done. Source code, and long boring tutorial about it. Really, check the tests here, they are special. It doesn't have "service" because the app is too simple, but I usually have a service layer as a files with exported functions. Error handling is in app.ts.
-
Rate my project made with Express + TS
I keep all routes in a separate file: routes.ts, in case of multiple API versions it could be "routes.v1.ts", "routes.v2.ts" and so on. v1 and v2 can reuse the same controllers.
-
Writing & organizing Node.js API Tests the right way
I wrote some tests for sample app as well, maybe could be interesting for you to check it out: here, criticism is welcome, just as I like to criticize
What are some alternatives?
survey-manager - A survey manager and creator project with node, typescript and react
projecthunt-api - API for projecthunt a project hunting platform
swagger-petstore
nodejs-integration-tests-best-practices - ✅ Beyond the basics of Node.js testing. Including a super-comprehensive best practices list and an example app (March 2024)
node-rest-starter - A Node.js starter containing common components and services as a reference API.
kysely - A type-safe typescript SQL query builder [Moved to: https://github.com/kysely-org/kysely]
domain-driven-hexagon - Learn Domain-Driven Design, software architecture, design patterns, best practices. Code examples included
wirepig - Better testing through the power of sockets.
Ts.ED - :triangular_ruler: Ts.ED is a Node.js and TypeScript framework on top of Express to write your application with TypeScript (or ES6). It provides a lot of decorators and guideline to make your code more readable and less error-prone. ⭐️ Star to support our work!
nodebestpractices - :white_check_mark: The Node.js best practices list (February 2024)
a12n-server - An open source lightweight OAuth2 server