git-archive-all
git-cache-tag
| git-archive-all | git-cache-tag | |
|---|---|---|
| 2 | 2 | |
| 9 | 0 | |
| - | - | |
| 0.0 | 0.0 | |
| over 1 year ago | over 1 year ago | |
| Shell | Shell | |
| MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
git-archive-all
-
Git archive checksums may change
- you have submodules (to which `git archive` is completely blind).
Note that `git-archive-all`[1] can help as long as your submodules don't do things like `[attr]custom-attr` in their `.gitattributes` as it is only allowed in the top-level `.gitattributes` file and cannot be added to the tree otherwise.
[1]https://github.com/roehling/git-archive-all
-
Why you should check-in your node dependencies
Thanks for sharing!
Depending on the context, if you don't want this in git history, and want to handle git submodules, there's also git-archive-all https://github.com/roehling/git-archive-all (if you like shell scripts, it is using bats for testing - it was the first time I heard of it)
git-cache-tag
-
Dura: You shouldn't ever lose your work if you're using Git
Oh wow, this seems pretty similar to this thing I wrote: https://github.com/unqueued/git-cache-tag
Which saves all uncommitted changes to a tag.
I wrote it because I wanted to have a complete snapshot of a build context. Sometimes composer or npm can't be relied upon to reproduce dependencies in the state they used to be, or I just want a cache of artifacts. It has been pretty handy.
-
Why you should check-in your node dependencies
I think that having rapid access to node_modules can be very helpful sometimes. The solution I came up with was this:
https://github.com/unqueued/git-cache-tag
It copies all untracked stuff (including node_modules) into a leaf tag. It is fairly easy to manage them, or find the latest one. And because they are leaves, they can be pruned and completely garbage collected when they aren't useful anymore.
I have been burnt many times by npm, and I use this script to guarantee that I have a stash of my node_modules, while also keeping my project small.
And I have diffed different snapshot tags to see which module changed that broke something.
And by leaving everything in unaltered text, it exposes it to git which does a great job at compression stuff, especially highly differential revisions of my node_modules.
A 500M node_modules from one of my projects only weighed about 100M extra, even with several snapshots. And I can just delete them anyway.
I need to work on it a lot more, it was just a quick and dirty solution when I had to work with React Native a few years ago.
What are some alternatives?
devtools-frontend - The Chrome DevTools UI
dura - You shouldn't ever lose your work if you're using Git
go-offline-maven-plugin - Maven Plugin used to download all Dependencies and Plugins required in a Maven build, so the build can be run without an internet connection afterwards.
cli - the package manager for JavaScript
aws-sdk-cpp - AWS SDK for C++
SIG-rules-authors - Governance and admin for the rules authors Special Interest Group
depclean - DepClean automatically detects and removes unused dependencies in Maven projects (https://dx.doi.org/10.1007/s10664-020-09914-8)
picosnitch - Monitor Network Traffic Per Executable, Beautifully Visualized
github - Just a place to track issues and feature requests that I have for github
node-http2 - An HTTP/2 client and server implementation for node.js