Publish to npm

[feross]

Please publish this to npm! 👍 The package name interact.js is available.

[feross]

Also, this library is excellent. Thanks!

[taye]

Please publish this to npm! 👍 The package name interact.js is available.

You can pull it into your project with

npm install --save taye/interact.js

I've discussed why I don't want to publish it to npm in #70

Also, this library is excellent. Thanks!

You're welcome!

[natew]

I feel like there's not much explanation there! Just want to throw in my +1 on publishing to npm, I think it would make the project more successful.

[feross]

I get that you don't want different names on npm and bower – it seems wrong and gross. But there's precedent for it, from a very popular library too, velocity.js. See: https://github.com/julianshapiro/velocity

bower install velocity
npm install velocity-animate

npm git installs are a bit of a second-class citizen. It adds another external dependency to your project install process (if either npm or github is down, you can't install/deploy), and commands like npm outdated report git deps as always outdated.

I'd just nab interact-animate or interact.js (despite npm's recommendation, some libraries still use .js, and it's fine to do so if there's no other good name available).

[taye]

@natew Thanks for your input. I often prefer to wait until more/stronger arguments come in before changing things (which is why I left this issue open).

@feross I didn't think that there was any difference between installing with a package name and installing with a git repo. I guess I'll publish it as interact.js then.

[feross]

Thanks!

[taye]

done

https://www.npmjs.org/package/interact.js

[anthonyborell]

@taye You guys should consider renaming the npm package to "interact-js" or simply "interact" like you have done with bower, as I am getting numerous issues when building and importing with typescript and aurelia because its looking for a file called interact.js and not a folder. I renamed the folder and this fixed my problems. However now, this breaks package.json