The drawback of this approach is that
atom-beautify will not update itself when a new version comes out. Instead, you have the ability to use any version of the package you want if you keep your repo up to date, because git lets you open old versions of files that have been saved (“committed” in the lingo) and you can see which versions of the code were released as new versions of the package. When you check out a different branch or commit, git actually rewrites every file it has been told to track (everything except what’s listed in
.gitignore) to the other state.
This particular bug is happening somewhere in the busy scramble of activity that happens when dozens of tiny Node packages are called down and assembled into the
node_modules/ folder, but it’s not a problem with the transfer of those files. Instead, some of the code that was written for Atom’s package manager, potentially code designed to prevent you from making a new download every time you use an especially common package like
underscore. The bug repeats for
atom-beautify, but not any other package so far. One of APM’s developers might be able to give us a satisfactory answer, but it’s unlikely to be something that the package author can do anything about.