routing-controllers
jest-extended
Our great sponsors
| routing-controllers | jest-extended | |
|---|---|---|
| 6 | 3 | |
| 4,330 | 2,291 | |
| 0.6% | 0.2% | |
| 9.0 | 6.7 | |
| 4 days ago | about 1 month ago | |
| TypeScript | JavaScript | |
| 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.
routing-controllers
-
Node.js 20 is now available
The standard is express. I say that with some glibness, but its the only true answer: a ton of the other higher level frameworks and pluggable middlewares still rely on the core express Request/Response types. And there are a ton of higher level frameworks, if the number of distinct replies wasn't obvious.
I really like express + routing-controllers [1], if you're on typescript.
[1] https://github.com/typestack/routing-controllers
-
Do you use Swagger/OpenAPI to document your APIs? If so, what is your preferred way to generate the docs?
I currently use https://github.com/typestack/routing-controllers and https://github.com/epiphone/routing-controllers-openapi with https://github.com/Redocly/redoc
- How to implement Socket.io using Typescript
-
Creating a web server with typescript, should I go for express or fastify? Which one has better packages for typescript integration? Any recommendations for packages for each?
If I don’t want to use nest then I would use express or koa with routing-controllers. Using this package you can write controllers with classes and decorators which is similar to nest js. There are a lot of other features too.
- Maintaining REST API Documentation with Node.js
- Great examples of idiomatic (backend) TS code
jest-extended
-
How To Use expect.objectContaining With Null and Undefined
I recently came across a workaround for this issue by using the expect.toBeOneOf() matcher from the jest-extended library. This matcher allows you to check whether a value matches one of the expected values, including null and undefined.
-
Node.js 20 is now available
Yes, a standardized expect would be nice, but care has to be taken to not bloat it.
Currently I use vitest and https://github.com/jest-community/jest-extended which gets you a reasonable amount of usable matchers.
-
The frontend tooling guide to improve Developer Experience
Jest-Extended: Additional Jest matchers
What are some alternatives?
tsoa - Build OpenAPI-compliant REST APIs using TypeScript and Node
Detox - Gray box end-to-end testing and automation framework for mobile apps
nestjs-commander - A module for using NestJS to build up CLI applications
lighthouse-ci - Automate running Lighthouse for every commit, viewing the changes, and preventing regressions
fastify-openapi-glue - A plugin for the Fastify webserver to autogenerate a Fastify configuration based on a OpenApi(v2/v3) specification.
jest - Delightful JavaScript Testing.
websocket-typescript
Cypress - Fast, easy and reliable testing for anything that runs in a browser.
openapi-typescript - Generate TypeScript types from OpenAPI 3 specs
phero - Full-stack type-safety with pure TypeScript
swagger-jsdoc - Generates swagger/openapi specification based on jsDoc comments and YAML files.
Standard - 🌟 JavaScript Style Guide, with linter & automatic code fixer