Bug report

Describe the bug

Currently, if the next build is targeted to serverless, the resulting files don't go through tree shaking.

To Reproduce

Checkout this repo: https://github.com/fernandobandeira/next-serverless-treeshakingissue
Just install and build the project, if you inspect the resulting index.js file, you'll see that it has 1mb and contains all of the icons from

Looks closely related to #779

I'm submitting a...

[ ] Regression
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

Middleware is being called for every endpoint a request route could potentially match.

If specify non-existed file with --file option, mocha throw expection.

./bin/mocha --file non-existed
/Users/mocha/node_modules/yargs/yargs.js:1163
      else throw err
           ^

Error: Cannot find module '/Users/mocha/non-existed'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:582:15)
    at Function.Module._load (internal/modules/cjs/loader.js:508:25

In the readme, the link to pronunciation won't play the pronunciation because it violates content Security Policy directive.

Refused to load media from 'https://raw.githubusercontent.com/avajs/ava/master/media/pronunciation.m4a' because it violates the following Content Security Policy directive: "default-src 

It would be nice to have an isSlug validator.

The spec defines /.well-known/change-password as a well known URL redirecting to the password change page

• Redirect user to /me/edit/password (res.redirect should be sufficient)
• Logged out users are already handled appropriately, they log in and are sent to the password edit page

Node version (or tell us if you're using electron or some other framework):

12.1.0

ShellJS version (the most recent version/Github branch you see the bug on):

0.8.3

Operating system:

Windows

Description of the bug:

sed is applied only once by line:
original archive:
import [COMPONENTNAME]Base from './[COMPONENTNAME]Base';
`const [COMPONENTNAME] = styled( [COMPONENTNAME]

Context

currently, I found nock and am trying to test out a http module flow. along the way, we require extracting the address() result object.

w/in the response, we have this event:

req.on( 'socket', ( socket ) => {
      console.log(socket);
      req[ '_socketAddr' ] = socket.address();
} );

What are you trying to do and how would you want to do it differ

This is wrong and needs some updates. exclude, specs, maxInstances, shardTestFiles, count, seleniumAddress are not capabilities.

https://github.com/angular/protractor/blob/master/lib/config.ts#L300-L322

Please submit PR's to the selenium4 branch.

Related: angular/protractor#5128

I am trying to run an express app through Visual Studio Code. I have a launch.json file with DEBUG defined like so:

        "env": {
             "DEBUG": "*"
        }

Here is a trimmed down version of my app.js file where you can see the bolded debug line that doesn't output to the debug console (Test 2). Test 1 before it outputs as expected. If I run this from the command li

Hi, if you are reading this is because you pretty likely don't know how to start 🤔 . Fair enough !

So, let's fix that 🚸 !

What should I know before start?

All here we are developers with different backgrounds, languages and objectives. But, all we must follow certain rules so we can understand each other and make the communication easier as possible. Please 👍 read your [code of conduc

AWS Lambda currently supports Node v10.x
Can you please support it.

As described at HabitRPG/habitica#9745 it's possible for the gem prize for a challenge to be null which results in the prize box on the challenge having a blank space where the number of gems should be, as shown in the screenshot below.

As I mentioned in one of my comments there a null prize d

There are a set of steps that would probably be useful in troubleshooting problems with Commitizen and Adapters. Over time it would be nice to have a place for them to be documented rather than being stuck in issues.