https://github.com/github/gitignore/pull/3651/files#r576363678

After running `yarn set version berry` and `yarn install`, the file `.yarn/install-state.gz` is created.

The documentation at https://yarnpkg.com/advanced/qa#which-files-should-be-gitignored mentions that this file should be ignored:

> .yarn/install-state.tgz is an optimization file that you shouldn't have to ever commit. It simply stores the exact state of your project so that the next commands can boot without having to resolve your workspaces again.

The documentation has a minor error; the generated file is `.gz` instead of `.tgz` (source: https://github.com/yarnpkg/berry/pull/998/files#diff-23dd4c2e823c25186f1107e88e962032R201)

Similar to #2608, it's the defacto tsc way now for adding typings locally.

Use real conventions (from the creators of dotenv)! https://github.com/bkeepers/dotenv#what-other-env-files-can-i-use

* Ignore files inside `.vscode-test` 

[vscode-test](https://github.com/microsoft/vscode-test) is a testing framework for vscode extensions. Inside the `vscode-test` folder are stored one or more versions of vscode, which are used for testing a vscode extension.

* Update Node.gitignore

* Remove conflicting gitignore lines, add reference

Ref (introduction of a new "public" folder in Next.js):
https://nextjs.org/blog/next-9-1#public-directory-support

* Improve solution to conflicting files

* Update Node.gitignore

* Fix coverage.lcov to *.lcov

Lerna is an increasingly popular tool within node ecosystem to manage package dependencies and having writes to a `lerna-debug.log` following the yarn and npm precedence when error is encoutered.

* [Node] Ignore diagnostic report files

* Add documentation URL

* Stricter regex

Project site: [link](https://fuse-box.org/)

Corroboration: [link](https://fuse-box.org/docs/development/configuration#cache)

Reason: Don't VC cache

Hopefully, I did this correctly!

Node.gitignore build/Release Compiled binary addons: http to https
https://nodejs.org/api/addons.html

This adds ignores for the `yarn-debug.log*` and `yarn-error.log*` files sometimes produced by the [Yarn package manager](https://yarnpkg.com).

Some .gitignore parsers interpret directory vs non-directory patterns strictly (e.g. monochromegane/go-gitignore), so a `node_modules` pattern would not necessarily match against a real `node_modules` directory. It's generally safe to add a trailing slash to directory .gitignore patterns.

Add `*.tgz`, the output of `npm pack`, or other build-steps.

Some popular applications (for example, Phusion Passenger) leave `*.pid.lock` file(s). For example, when you type `passenger start` with simple express app listening on port 3000, it leaves the following files:

* `passenger.3000.pid` (removed when passenger stops)
* `passenger.3000.log`
* `passenger.3000.pid.lock`

While `*pid` and `*.log` are ignored, `*.pid.lock` remains unignored. Phusion Passenger is quite popular, and `*.pid.lock` file should be ignored.

[nyc](https://github.com/bcoe/nyc) is quite popular, and under some circumstances it writes to `.nyc_output` directory. This directory should be ignored by default.