The current WHATWG URL parser implementation is written in C/C++ and incurs a fairly significant cost crossing the JS/C++ boundary. It should be possible to realize a significant performance improvement by porting the implementation to WASM (similar to how the https://github.com/nodejs/undici project has seen a massive performance boost out of moving llhttp parser to wasm).

If someone wanted to

What example does this report relate to?

with-Apollo

What version of Next.js are you using?

10.0.0

What version of Node.js are you using?

10.14.2

What browser are you using?

chrome

What operating system are you using?

macOS

How are you deploying your application?

Other platform

Describe the Bug

The Apollo client query response is s

e.g. isPassportNumber, etc.

https://docs.nodebb.org/installing/os/osx-mavericks/

Though we do have iOS devices for mobile testing, our core team doesn't actually own a mac (fight this war somewhere else :P). Would anyone with access to one mind testing and updating this page please? :)

More importantly the instructions for redis should be switched to mongo as it is our default recommended install; you can look at the

The Vue select component looks to have a small issue with the hit area.

There is a single pixel (I think only 1xp) between items in the select dropdown, and when clicked it closes the Select.

This is only a small problem but could cause frustration when a user thinks they have selected an item and then save, not realising it hasn't been changed.

![directus-v-select-single](https://user-im

Context

This isn't really a feature request, as what I need is possible with nock as-is. But I spent several hours searching, reading old issues and searching through the source code to find the solution, so I thought this might help others.

I am testing code that accesses a service that sets the statusMessage of the response, as well as the statusCode. I am using nock to mock the server