node
Node.js is a tool for executing JavaScript in a variety of environments. JavaScript had humble beginnings as a language that lived only in web browsers, but the Node.js project has expanded its reach and helped make it the most popular programming language in the world. Node.js extends the creative potential of people with web development experience, enabling a new generation of developers to create servers, command-line tools, desktop apps, and even robots.
Here are 17,591 public repositories matching this topic...
Bug report
Describe the bug
I just cloned the example project with-firebase-authentication and followed the instructions within the README.md to setup. After running the command npm run dev and went to my browser on localhost:3000, I received an error within my terminal.
Error: Error serializing `.user` returned from `getServerSideProps` in "/".
Reason: `undefined` can
-
Updated
Apr 24, 2020
-
Updated
Apr 23, 2020 - JavaScript
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
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.
-
Updated
May 5, 2020 - JavaScript
-
Updated
Apr 14, 2020 - Go
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]
-
Updated
May 5, 2020 - JavaScript
-
Updated
May 5, 2020 - JavaScript
-
Updated
Apr 30, 2020 - JavaScript
-
Updated
Apr 20, 2020 - JavaScript
-
Updated
May 6, 2020 - TypeScript
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
-
Updated
Apr 30, 2020 - JavaScript
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.
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
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
AWS Lambda currently supports Node v10.x
Can you please support it.
-
Updated
Apr 21, 2020 - CSS
-
Updated
May 1, 2020 - TypeScript
Created by Ryan Dahl
Released May 27, 2009
- Organization
- nodejs
- Website
- nodejs.org/en
- Wikipedia
- Wikipedia


What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
Reproduces all the time.
What is the expected behavior?
Should not cause an