• 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

When running next using Yarn 2 and visiting a page in the browser that doesn't exist, the 404 error page never shows up. Instead it loads forever ("waiting on localhost...") and then eventually errors with ERR_EMPTY_RESPONSE.

But the terminal shows that the page was compiled:

[ event ] build page: /next/dist/pages/_error
[ wait ]  compiling ...

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 :)

There is no "pre-deploy" hook listed here as an option at https://pm2.keymetrics.io/docs/usage/deployment/. It should also be mentioned that this hook will run BEFORE git pull occurs, e.g. you may want to suggest to users to put git reset --hard as the pre-deploy hook in case their files such as yarn.lock change frequently, or localization occurs.

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.

I'm getting bit with failing documentation builds because I'm writing docstrings that JSDoc doesn't like (specifically, TS-style). But there's no linting happening before getting to Netlify.

We may be able to make JSDoc just check the syntax and exit (and make it part of the lint scripts).

This is moot if we want to move forward with maintaining our own TS types (for which there is an op

Spurred by conversation in avajs/ava#2449 and avajs/ava#1485 we'd like for our assertions to return booleans. true when they pass, false when they fail. This does not apply to the throws() and throwsAsync() assertions.

Failing assertions will fail the test, but do not throw exceptions. This means your test does not stop executing. Usua

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

[email protected] 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] ../.

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]

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

Is there an overview, how the config object for the constructors of the neural network are defined?

This would be interesting:

• Has brain.NeuralNetwork and brain.recurrent.RNN the same config attributes?
• What is the description of the inputSize attribute?

Thank you for the great work with this library, it is realy amazing!

I have a feeling that most people use async/await in new code, and none of the examples use it.

Also, from browsing random issues, better tests will be written using this structure. For example #543 is caused by not using async/await in tests.

// This passes!
it("should reset", async () => {
        request(app)
            .get("/reset")
            .expect(205);
});

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

https://www.apollographql.com/docs/apollo-server/data/errors/#codes

Mentions that:

In addition to stacktraces, Apollo Server's exported errors specify a human-readable string in the code field of extensions that enables the client to perform corrective actions. In addition to improving the client experience, the code field allows the server to categorize errors. For example, an Authenticat

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

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@

I'm submitting a ...

• bug report
• [ X] feature request
• question

PostGraphile version: 4.4.4

postgraphile should honor variables in query string as defined in https://github.com/graphql/express-graphql#http-usage when the query is provided as post body.

with the following exampl

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 there!

Thanks for submitting an issue to Protractor.

To help us help you better, please do the following before submitting an issue:

1. Review the questions section of CONTRIBUTING.md.
2. Make sure you are not asking a usage or debugging question. If you are, use [StackOverflow](http://stackoverflow.com/

Hello,

Im new with node, its possible to you improve instalation docs for 'standalone' server installation ?

How to install latest node, npm, and dependencie to run n8n with

npm install n8n -g

example: im running ubuntu 16.04.

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