Build artifacts should be in default .gitignore
See original GitHub issue- Laravel Mix Version: 1.4.2
- Node Version (
node -v
): 7.8.0 - NPM Version (
npm -v
): 4.2.0 - OS: Windows 10
Description:
Laravel’s default .gitignore
does not contain Mix’s build artifacts, such as public/mix-manifest.json
as well as the public/js/app.js
and public/css/app.css
that come configured out-of-the-box. This requires extra work from people that are using laravel-mix (to manually add the files to the .gitignore), and might cause people to accidentally commit them to source control.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:39
- Comments:11 (3 by maintainers)
Top Results From Across the Web
Build artifacts should be in default .gitignore · Issue #1159
Laravel's default .gitignore does not contain Mix's build artifacts, such as public/mix-manifest.json as well as the public/js/app ...
Read more >Prevent build artifacts from going into revision control
how do I create .gitignore and prevent build artifact from going into revision control? how do I do it exactly? can anyone give...
Read more >Git Ignore File: How and When to Use It
Artifacts are produced throughout the development process. These large binary assets can be completed builds, precompiled headers, ...
Read more >Use the .artifactignore file - Azure Artifacts
.git file is ignored by default if you don't have an .artifactignore file. You can re-include it by creating an empty .artifactignore file....
Read more >gitignore file - ignoring files in Git
Ignored files are usually build artifacts and machine generated files that can be derived from your repository source or should otherwise not be...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
public/mix-manifest.json
should be committed.Sure, but you shouldn’t check it in to source control. Instead, running
npm run prod
should be part of the deployment script. 👍