> Does "NPM installs the target module" mean it's pulling and/or updating
its sources to a VCS?
NPM decided that releases are part of a module. This module should be
release explicitly by the team/developer in charge for the module, and the
module version is consequently bumped after.
So developers that just want to use a module, do not have to worry where
that project VCS is, if stills online or not, if exists or not. All this
factors are mitigated and handled by NPM, due to its release/usage
Example: Given a project has version 1.0.0 and the developer executes npm
publish, When the module is pushed to NPM, Then your module is released to
public usage, And your package.json (file that contains info about the
module + version) has the version bumped automatically, And the developer
should not be able to release twice under same version.
In the other hand, Go decided (or the absence of a early stage design
decision caused this) that releases are linked to explicit commits, so VCS
was added to equation to mitigate the problem + enabling people to use
external projects into their Go modules... So several projects have been
created to address the issue, like godeps, gm, glide. But (correct me if
I'm wrong) there is no central repository for releases in Go ->
On Thursday, October 13, 2016 at 11:28:28 AM UTC+2, Jan Mercl wrote:
> On Thu, Oct 13, 2016 at 8:18 AM Thomas Modeneis <thomas....@gmail.com
> > I hate comparing Go with Node, but (I'm sorry)... How about doing the
> same that NPM does ? NPM installs the target module + target version. End.
> I'm not familiar with Node. Does "NPM installs the target module" mean
> it's pulling and/or updating its sources to a VCS?
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.