Remove webpack generated files out of git?
See original GitHub issuePros of removing webpack
generated files out of git are obvious. (clean code commit & review and less conflicts).
How about we combine webpack
and node hashbrown.js
into npm start
shortcut command, to compile the static files from src every time user start the application?
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Delete unused webpack chunked files - Stack Overflow
So doing a git checkout to the previous version followed by a npm ... Open raw file view and copy it to index.js...
Read more >Prevent files created by other plugins from being removed ...
How can I prevent files built by other plugins from being removed on rebuild of unrelated files, without having to explicitly list those...
Read more >remove-files-webpack-plugin - npm
A plugin for webpack that removes files and folders before and after compilation.. Latest version: 1.5.0, last published: a year ago.
Read more >Output Management - webpack
In general it's good practice to clean the /dist folder before each build, so that only used files will be generated. Let's take...
Read more >Set Up a GitHub Project with node_module - Pluralsight
If node_modules is already a part of a repository then it can be removed using the git rm -r --cached node_modules command, though...
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 Free
Top 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
@AndreLion on the
v1.2
branch, if you don’t mind.@AndreLion merged 👍