i noticed this too, been trying to use this with 0.7
what causes npm install different than git clone
when i do npm install of a plugin, its diferent code base than git clone of the repo, same version in package.json as the git repo.
@chrismccoy which plugin are you trying to install?
same version in package.json doesn't mean code will be the same... there might be more check-in's after it's published to npm and usually version on github in package.json is not changed until it's ready to be published to npm again.
jarey last edited by
The mantainer could have just published to npm and evolved the code in the repo without updating the version according to a new release. If he/she makes the change of version in package.json just before publishing to npm, you can have the fepo with and 'old' version and new code while evolving to the next 'npm release'.
gitis a tool for versioning source code.
npminstead is a package manager, so it's targeting the production code.
Basically you have this workflow
git v0.1.0 -----> compilation -----> npm v0.1.0 | | code changes v git v0.1.1 -----> compilation -----> npm v0.1.1
For any kind of software; You don't publish binaries/production code within
git. Only if the source code equals the production code (thus there is no compilation step involved) you'll have the same within
It gets worse if people publish their binaries/production code alongside their source code within
As a rule of thumb:
git(ore more general VCS) is for publishing source code; package manager are for publishing production files.
the expiring downloads plugin.
on the npm install one, only a few js files are present.
here is npm v0.2.2
looking to modify the default markup when the upload is complete.