node

Version

v16.10.0

Platform

Linux solus 5.14.7-198.current #1 SMP PREEMPT Wed Sep 22 16:02:46 UTC 2021 x86_64 GNU/Linux

Subsystem

stream

What steps will reproduce the bug?

const {Writable} = require('stream');

class X extends Writable {
    async _destroy(error, callback) {
        (async () => {
            await new Promise(resolve => setTimeout(

What version of Next.js are you using?

11 and 12 (only with Webpack 5)

What version of Node.js are you using?

14 and 16

What browser are you using?

does not matter

What operating system are you using?

Windows 10

How are you deploying your application?

SSG and/or Vercel Deploy via GitHub

Describe the Bug

**The issue only occurs with Webpack 5

I would like to give this to the people who are new and would like to start contributing to validator.js.

The current version in isMobilePhone validation, we have less than 195 phone validations i.e

In the code https://github.com/validatorjs/validator.js/blob/master/src/lib/isMobilePhone.js, the validations exist from line 5 to line 119, which means we have probably 119 - 5 countries phone

I have a project that is in a monorepo and uses yarn right now.

I'm considering migrating to pnpm for the monorepo, as well as all other projects I contribute to, as I have a small SSD as local storage (and with Windows...). However, it would be ideal if there was compatibility between yarn's workspaces and pnpm, so that we don't have to jump "all in" to it.

To this end, yarn allows packages

As @jaycammarano correctly pointed out, the gradient in the time-series panel in Insights is scientifically inaccurate. We should add a way to opt-out of the gradient design element for scientific accuracy.

Discussed in verdaccio/verdaccio#2155

The current progress could be tested via

pnpm install
pnpm build
pnpm debug:fastify

or

npm i -g verdaccio@6-next
verdaccio fastify-server

The main idea is launch fastify with next major but under a flag, so could be tested for a period of time until replaces completely Express server.

Yuck.

Whoever wants to tackle this, .chats-full should be a flex item instead.

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