• Version: v10.x
• Platform: all
• Subsystem: repl

What steps will reproduce the bug?

$ node
> function foo() {
... let n = 10n;
Thrown:
let n = 10n;
           ^

SyntaxError: Unexpected end of input
>

How often does it reproduce? Is there a required condition?

Reproduces all the time.

What is the expected behavior?

Should not cause an

Bug report

Describe the bug

A clear and concise description of what the bug is.

In my global.scss file that is imported by src/pages/_app.tsx:

@use '@material/textfield/mdc-text-field';
@use '@material/select/mdc-select';

body {
  margin: 0;
  padding: 0;
  outline: 0;
  overflow-x: hidden;
}

Those @use statements fail however because the default `sass-

It would be good if the docs and --help output could mention that nvm install installs and uses the given Node version. I've probably wasted hours typing nvm install __ && nvm use __, - just discovered the second part has been unnecessary since this was fixed in 2014 :)

What's going wrong?

The docs say that the default exec_mode is fork. However, when exec_mode is not defined in the config, my processes start in cluster mode.

How could we reproduce this issue?

A config without exec_mode defined.

I'm submitting a...

[ ] Regression 

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

Doc about endpoint testing states:

If you start your server using a test.before() hook you should make sure to execute your tests serially

This is not clear to me why is better to have tests in serial in that case. Anyone can explain me?

e.g. isPassportNumber, etc.

There's a section about Uninstall existing npm, but the recommendations for upgrading are scattered in the issues.

The relationship between node, npm and nvm is not clear and it's not obvious if upgrading npm should be done through nvm or at least in a way that doesn't break nvm.

On Windows10 machine, following README installation instructions:

c:\code\mean>npm start

mean@2.0.2 start c:\code\mean
concurrently -c "yellow.bold,green.bold" -n "SERVER,BUILD" "nodemon server" "ng build --watch"

[SERVER] [nodemon] 1.18.9
[SERVER] [nodemon] to restart at any time, enter rs
[SERVER] [nodemon] watching: .
[SERVER] [nodemon] starting node server
[SERVER] ../.

https://docs.nodebb.org/configuring/databases/

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]

What is wrong?

npm run build fails with slightly modified color contrast example

Where does it happen?

There are two mentions of a reactide.config.js file in the README:

The component tree works out-of-the-box by finding the entry point to your React application that you provide inside the reactide.config.js file.

Go to the reactide.config.js file and change the .html and .js entry points to the relative path of your respective files.

But I could not find any examples or documentation

By performing a unit test of a controller as proposed in the Nest.js Documentation I found a really strange behavior when trying to set the header { accept: "application/pdf" } which triggers a jest.setTimeout.Error.

It is curious because I have another test, which is theoretically the same but the difference is `{ accept: "

What is the expected behavior?
If I use

nock('https://example.com/my_url', { reqheader }).log(console.log);

I would expect that a request to https://example.com would be checked against that route and that the logging would show that.

What is the actual behavior?

Nothing is logged to the console if the headers do not match the specified reqheader
This is confusing be

• Add option to enable analyze on queries only
• Add option to export as JSON rather than text (for import into https://tatiyants.com/pev/#/plans/new)
• Add button (or similar) to easily copy the SQL query or explain results

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

root@syzoj-test-vm:~/syzoj-ng-app# commitizen init cz-conventional-changelog --yarn --dev --exact
Attempting to initialize using the npm package cz-conventional-changelog
yarn add v1.19.0
[1/4] Resolving packages...
[2/4] Fetching packages...
error Incorrect integrity when fetching from the cache
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
root@

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

When you're viewing your private message conversations with other players, all your previous messages show your current avatar.

The expected behaviour is that they show your avatar at the time that the message was sent.

The expected behaviour can be achieved by using the avatar appearance data that's stored in each of the chat messages. For example below is one of the PMs I've sent and the

It would be great if all of these projects included a devcontainer dir & docker file so that they can be run without any machine setup or config