Publish to npm

[th3fallen]

The package currently has a package.json but it can't be found in the NPM Registry. Could it be published there for all of us folks using npm/etc?

[victorjonsson]

Duplicate of #238

It's currently only possible to install this plugin using bower. Whether or not the plugin should be available via npm is not yet decided.

[th3fallen]

Why would it not be? its literally a single command to run to publish it, not like its going to break anyones back?

[Igloczek]

Bower is going to die soon, everyone switching to npm.

[laander]

+1 on this, npm please :)

[victorjonsson]

Hm... I wouldn't draw the conclusion that bower is dying looking at the stats http://bower.io/stats/

My personal opinion is that you shouldn't use npm for distribution of a clientside-only javascript library. I would not like to entangle server-only code with client-only code. This plugin is not a node module, and should therefor not be published on npm, which is meant for distribution of node modules.

But of course, If "everyone" switches to npm and it becomes the de facto standard for distribution of client-side libraries, it would change my perspective on this... Many large js-project uses npm as well as bower and some decide to have the main project distributed via bower and then have a "node"-fork (specifically for running the code on a node server) published on npm.

How ever, anyone can fork this project and publish it on npm...

[seiyria]

It seems there's a misunderstanding. It's one I had a long time ago, as well - npm is not just for node/server components. Plenty of popular libraries (angular, angular/material, lots of others) publish on npm, and those are not at all server-side compatible.

I won't suggest that bower is dying, but publishing only on bower is not a wise choice. More and more people are using browserify, and other tools to make this workflow work. It's simply alienating users if you don't intend to at least use npm. Note I don't suggest to publish to every package manager - that's insane. However, npm and bower are the two to use, if any at all (especially because bower just uses github). If you only had to have one, I would recommend npm (it can be browserified very easily).

Now, to the point of forking it. Lots of people maintain bower forks of tools (I've never actually seen anyone do it for npm), but that requires updates to be separate from the build process (I'll touch on this later). This means that someone else has to keep up with your changes, which is nothing short of a pain. Don't put that pain on anyone else.

I see you have a gruntfile, which means you're already familiar with task automation. That's great! If you don't want to deal with manually publishing to npm, add a task in your gruntfile. I can't personally recommend a module, but this one looks similar to the one I use with gulp.

[victorjonsson]

I believe it's more a matter of opinion than a misunderstanding :) No but seriously, I know it came off as if I were against publishing the plugin on npm, which is actually not the case. It was more meant as an explanation on why I haven't put any effort into it. I'm not using browserify and I install all client side dependencies using bower.

It was incorrect of me to say that "npm is meant for node modules", I realize that now (after having read your words seiyria, and updated myself on the subject). I'm still uncomfortable with the thought of installing client side libraries using npm (except in the case of browserify) but it should probably be beneficial to the project if I made the plugin available through npm.

[laander]

@victorjonsson apart from Browserify, Webpack is growing too and npm is by far the easiest package manager for that purpose (just require() and webpack takes care of the rest). Just my 2 cents

We are in the process of switching from Bower to NPM too as we are starting to use Browserify. So I would also love to see this published on NPM.

[th3fallen]

@glamic-ep @laander since he doesnt want to publish himself for whatever reason i published it myself so i could continue using it https://www.npmjs.com/package/jquery-form-validator whenever he wants to publish it i'll happily remove it from my listing but i cant wait any longer for something so trivial.

nice!

[th3fallen]

i mean its literally git clone {repo} and npm publish boom done... no idea why this needs this level of debate

[victorjonsson]

@th3fallen Could you be so kind and add me as the owner of the npm package?

[th3fallen]

@victorjonsson done. as soon as you confirm i'll remove myself as a collaborator just want to make sure it sticks before i do.