Remove .gitignore from bower package
See original GitHub issueExpected Behavior
It should not ignore the dist directory when chartjs is installed using bower.
Context
We check-in the dependencies into our source control, because we don’t mirror bower packages locally on our servers. When we add Chart.js as bower dependency, the dist folder got ignored from the source control, because of the .gitignore in the bower package. Is it possible to remove the file in the bower package, or is it needed?
Environment
- Chart.js version: 2.4.0
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Should bower_components be gitignored? - Stack Overflow
The advice on the official Bower page to check installed packages in to source control was removed in 2014: github.com/bower/bower.github.io/ ...
Read more >Bower, an assets package manager - Synbioz
Uninstall packages. To uninstall packages, use the following command line : bower uninstall my_package_name. If you use the bower.json file, remove the package...
Read more >How to drop Bower support? · Bower blog
Don't remove your component from Bower registry (via bower unregister ). To understand why these steps are necessary you need to know how...
Read more >Remove Bower from your build script - ThoughtWorkshop
When the Knockout maintainer released the v3.1 bower package, they made a mistake in bower.json config file, which packaged the spec folder ...
Read more >Remove bower and add yarn support · f442646269 - OpenDev
1 .eslintignore · 1 .gitignore · 12. Gruntfile.js · 2. bin/bootstrap.sh · 4. bin/build.sh · 30. bower.json · 2. karma.conf.js · 58. package.json....
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

@simonbrunel I don’t have a problem with trying it. I don’t think it will break anything, but a quick google couldn’t confirm that.
I don’t think we want to deal with a different repository and change our automated build process for this specific bower use case. Having
.gitignoreinbower.jsonlooks like the way to go, so we can definitely try this for 2.5. @chartjs/maintainers do you see any (compatibility) issue with that approach?Still,
git add --forcewould solve your issue immediately.