-
Notifications
You must be signed in to change notification settings - Fork 1k
Publish as npm package #828
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@metallium You may be more familiar with npm than I am, have a look here and let me know if there are any issues: https://www.npmjs.com/package/jquery-ui-timepicker-addon I'm use to being a consumer of npm, but not a publisher so I may need to do something differently?... |
one thing left: re-publish package with valid "version" field in package.json please (it is already fixed in repository) thanks! |
Ok, I'm showing on npm package page 1.5.5. Is that what you're seeing? |
it's ok. |
Can you please publish v1.6.1 to npm? Thanks. |
+1, that'd be great (actually that'd be 1.6.3 now) ! Thanks in advance! |
Yes please, if you get a chance that would be great. |
It would be really great if the latest release (1.6.3) would be available to npm. |
Me too - please update npm package! |
@trentrichardson Could you please publish the latest version to npm? |
Ok, published 1.6.3: |
Thanks! 👍 |
It would be great to have this addon published in npm registry. Guys building their assets using browserify/webpack definitely need that (that might be the only package that requires bower ;) )
Thanks!
The text was updated successfully, but these errors were encountered: