laravel/.gitignore

/.phpunit.cache
/node_modules
/public/build
/public/hot
/public/storage
/storage/*.key
/vendor
.env
.env.backup
.env.production
Homestead.json
Homestead.yaml
auth.json
npm-debug.log
yarn-error.log
/.fleet
/.idea
/.vscode
[10.x] Adds PHPUnit 10 support (#6052) * Adds PHPUnit 10 support * Reverts `noNamespaceSchemaLocation` * Improves PHPUnit configuration file 2023-02-07 15:26:27 +00:00			`/.phpunit.cache`
Add "node_modules" to .gitignore Seems sensible if Laravel's going to push Elixir. A person unfamiliar with the node ecosystem should be able to use Elixir with ease, however I don't feel they should necessarily know up-front that they should add node_modules to their global .gitignore file. 2015-02-01 11:16:11 +00:00			`/node_modules`
[9.x] Vite (#5904) * Use Vite * Gitignore Vite build directory * Use CSS entry points * Update plugin * Linting * Update plugin 2022-06-23 04:07:47 +10:00			`/public/build`
Remove the hot file from versionning Following https://github.com/laravel/framework/pull/17571, I was correctly pointed that the small proposition should be made over here. Here's a copy / past of my message, for clarity's sake. --- When you run `npm run hmr`, a `hot` file is created to the public folder for the `mix()` helper to know if it has to server from the webpack server or not. This file does not go away until we run `npm run dev` (or `watch`). True, if we use `npm run production` in our production server it goes away too, but in case we don't make it go away in development, I don't think it's necessary to version it. 2017-01-26 21:22:52 -05:00			`/public/hot`
Sorting gitignore file 2017-04-03 21:06:10 +02:00			`/public/storage`
Ignore Passport-generated OAuth keys These files should not end up in source control IMO. And even though Passport is a separate package it is a first-party one and the base Laravel install should be "prepared" for it. What do you guys think? 2016-10-12 15:51:50 +03:00			`/storage/*.key`
Fix order Fix .gitignore items in alphabetical order. 2016-08-22 17:02:27 +07:00			`/vendor`
Update .gitignore 2018-12-01 10:53:17 -06:00			`.env`
wip 2021-01-12 14:02:00 -06:00			`.env.backup`
ignore .env.production (#6004) 2022-10-06 22:02:37 +08:00			`.env.production`
Ignore Homestead.json 2015-07-25 12:57:52 -07:00			`Homestead.json`
Fix order Fix .gitignore items in alphabetical order. 2016-08-22 17:02:27 +07:00			`Homestead.yaml`
Update .gitignore (#5924) 2022-06-30 15:31:18 +02:00			`auth.json`
Ignore the npm debug log When an NPM run fails, is created a npm-debug.log file. This file can be ignored and should not be published on a Git based repository. 2017-04-18 20:58:22 -05:00			`npm-debug.log`
Ignore the Yarn error log Like the npm error log, this file can also be ignored. [See also](https://stackoverflow.com/questions/42592168/should-i-add-yarn-error-log-to-my-gitignore-file) 2017-07-04 15:25:06 +01:00			`yarn-error.log`
Add /.fleet directory to .gitignore (#6011) 2022-10-17 16:18:45 +02:00			`/.fleet`
add .idea and .vscode to gitignore (#5615) Add folders to gitignore. The same exclusions exist in the laravel / framework gitignore. 2021-05-24 10:19:41 -03:00			`/.idea`
			`/.vscode`