Is it possible to render the graphiql documentation on a separated web page? Just the same, what makes graphiql, but without the possibility to send / explore GraphQL queries.

The reason is, that our graph(i)ql end points need special authentication. For the access to the documentation we do not need it.

I was in trouble when managing my document with mongo express.

It cannot show the detail of a document which have number type id.

repro steps:

1. insert a doc with a number type id

{
    "_id": 123456,
    "message": "another field"
}

2. find the document we just insert above and click it
3. an error is shown on the screen: Document not found!

can anybody help?

If not for some particular exceptions, the status code returned from our WebAPI on error is always 500, regardless of the kind of error.

If an object already exists, for example, it should be returned as 409. If the object does not pass the schema validation, it should be a 415.

Go through the whole WebAPI and verify that the status codes are being returned correctly.

Hint: Error cl

uploadTimeout option defaults to 60000 in the source code, which is missing from the list of options specified in README.md file.

Looking for help to improve the examples READMEs, particularly examples/3-eov-operation READMEs

When a user does a password reset / changes his password, it makes sense to drop all sessions for that user. Currently the user id is stored inside a json blob on the session, so it becomes very inefficient to query for all sessions that belong to a specific user.

In issue #53 ( chill117/express-mysql-session#53 ), it was suggested that one way to workaround this issue

I'm trying to use language detection feature of this package but I can't. It seems like I need to implement both wire up i18next to request object and then language detection is that right?

All I want to do is to make i18next-express-middleware read and write language from my cookies.

Now most of our custom response examples are express.js dependent. And some of our officially supported implementations(like lite-server) don't use express. So updating or adding some examples that will work within all type of servers will be great.

I have the following Schema

    new querySchema({
      type: String,
      garment: String,
      brand: String,
      supplier: String,
      name: RegExp
    })

Haven't touched anything regarding pagination or limit, however after updating to 2.1.3 to include the cache problem, which I was having as well, this happens:

http://localhost:9000/branch-products?sort

As of #43 the whole ntlm client code is separated in a dedicated repository to include it for other authentication mechanics.

To reflect this change the existing ntlm client code in this repository should be removed and the documentation should be update to refer to the other module / repository.

There is an example in the README but generally there is a clear lack of documentation.

I would encourage someone to add basic documentation on each of the functionalities supported by this library: what does the functions do, what are the parameters and structures and what's the expected usage?

Implementation was done in #219, documentation is still missing. We should add an example with a concrete use case, for example passing a custom userAgent and/or measuring response times.

added 104 packages from 224 contributors, removed 129 packages, updated 398 packages and audited 891680 packages in 81.255s
found 16330 vulnerabilities (3 moderate, 16326 high, 1 critical)
  run `npm audit fix` to fix them, or `npm audit` for details

😱