-
Updated
Feb 15, 2022 - TypeScript
Fastify
Fastify is a web framework highly focused on providing the best developer experience with the least overhead and a powerful plugin architecture.
Here are 871 public repositories matching this topic...
A recipe with Mocha
Enrich our DB model
It looks like the Mercurius Gateway service expects "errors" to exist in the response, however, if I have a fastify plugin that throws an error before it ever hits GraphQL, then the gateway emits an error.
{
"errors": [
{
"message": "Cannot read property 'profile' of undefined",
"locations": [
{
"line": 2,
"column": 3
}
-
Updated
Feb 15, 2022 - TypeScript
-
Updated
Jan 24, 2022 - TypeScript
LDAP support
🚀 Feature Proposal
Login using LDAP account.
Motivation
A lot of companies use LDAP as their login system, so I thought that it could be useful to incorporate to HospitalRun
-
Updated
Feb 10, 2022 - JavaScript
Add support to ESM
Prerequisites
- I have written a descriptive issue title
- I have searched existing issues to ensure the feature has not already been requested
🚀 Feature Proposal
Frequently modules are dropping support to CommonJS and in order to keep it up to date, we should support the ESM as soon as possible
Motivation
Example
_No r
Prerequisites
- I have written a descriptive issue title
- I have searched existing issues to ensure the bug has not already been reported
Fastify version
3.27.1
Plugin version
2.15.0
Node.js version
14.18.2
Operating system
Linux
Operating system version (i.e. 20.04, 11.3, 10)
20.04
Description
If you move app/test/routes/example.test.ts to `app
-
Updated
Feb 14, 2022 - JavaScript
-
Updated
Feb 1, 2022 - JavaScript
🚀 Feature Proposal
Have an option to slow down responses instead of returning 429 errors.
Motivation
By having the option to slow down responses would deter scrapping of data from a server which would put an additional load on the server while still enabling responses for cases where user may not be actually scrapping, but just that there are many machines surfing the webpage under
🚀 Feature Proposal
When using the onError hook to log errors to monitoring services, it would be great to have access to the original error.
However this is not currently possible with fastify-sensible customErrorHandler, because it [creates a new Error](https://github.com/fastify/fastify-sensible/blob/master/index
-
Updated
May 14, 2021 - JavaScript
Improve codebase
The actual options for getHeader is not compliant to the fastify codebase that support the chaining-call:
ex: this.header('Content-Type', 'text/html; charset=' + charset).send(html)
It would be awsome if @momofan or @florianb could work on this
Mode info on how to implement this improvement:
https://github.com/fastify/point-of-view/blob/b7345f0601ec0e789cae535cf96bc14ac42ac04d/in
-
Updated
Feb 6, 2022 - TypeScript
Prerequisites
- I have written a descriptive issue title
- I have searched existing issues to ensure it has not already been reported
Fastify version
latest
Plugin version
latest
Node.js version
14
Operating system
Windows
Operating system version (i.e. 20.04, 11.3, 10)
win10
Description
yo your origin is pointing to nothing. How to fix this? I kno
-
Updated
Feb 9, 2022 - TypeScript
-
Updated
Sep 21, 2021 - JavaScript
Created by Matteo Collina
Released October 2016
- Organization
- fastify
- Website
- fastify.io
Clone the example app, only use Mocha instead of Jest
Before picking this issue, it's recommended to have a short tech planning chat here and only then upon sync to get up to speed.