Fastify

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.

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
        }
   

🚀 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

Link to HospitalRun/hospitalrun-frontend#1288

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

fastify/benchmarks#216

Example

_No r

It would be great if ESM projects could export const options when using the --options flag.

Like this:

export default async (fastify, opts) => {
  // ...
}

export const options = {
  maxParamLength: 200,
}

For now, this seems to work:

async function server(fastify, opts) {
  // ...
}

server.options = {
  maxParamLength: 200,
}

export default serv

Prerequisites

• I have written a descriptive issue title
• I have searched existing issues to ensure the bug has not already been reported

Fastify version

latest

Plugin version

master

Node.js version

16

Operating system

Linux

Operating system version (i.e. 20.04, 11.3, 10)

github actions

Description

The following are failing:

• https://github.co

🚀 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

This is not an issue, I just don't know how to exclude minifier for spesific routes?
Is this possible? how?

Thank you.

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