1. SvelteKit - added ignore for cache directory
2. .env.example - included for documentation
3. Vite - added ignore for log files
4. Firebase - added ignore for cache directory
- it is contained within `node_modules/`, which is already ignored
- the previous versions, which were not in `node_modules/`, did not have a period at the beginning of the filename
Changelog with proof here:
ba4b2db1f2/pnpm/CHANGELOG.md (L3330)
- microbundle hasn't used these directories in 3+ years
- d0e66da957
- and rollup-plugin-typescript2, which microbundle depends on and which
actually created the dirs, hasn't used them in ~3 years either
- ffda2e539b
- I help maintain rpt2 and formerly solo-maintained TSDX for ~1.5 years,
which, as a fork of microbundle, has similarly used those directories
in the past until I changed them
- 55c0d47c0b
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)
* 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
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.
