-
Notifications
You must be signed in to change notification settings - Fork 82
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
Publish latest version to NPM #28
Comments
nope. :) i've added you to the team though. i'd love if this and any of the other packages in this organization were still maintained. give me your npm username so i can give you publishing rights too! |
@jonathanong , you're not the owner of this repo at npm, you may need to contact the publisher. |
oh shoot. i'm okay with that too. |
@raquelxmoss you can have the latest version here https://www.npmjs.com/package/textarea-caret |
@chemzqm Ta |
I just confused myself by assuming npm's |
we also need a maintainer for this repo. anyone willing to maintain this? ill give them admin rights so they can change the header and readme |
@jonathanong: I have resumed maintenance of the project and would like admin rights. |
Any update on this? |
i don't have access to |
Hey guys, We'd like to resume maintenance of this package, and to publish new versions on NPM. Who can add me as an owner for the @chemzqm per your previous comment, and I see you listed as a contributor on NPM. @ashubham, per https://www.npmjs.com/~ashubham @ile / @ikkah since @dmacfarlane mentioned you, though it seems you published a 2015 fork. |
@dandv You are now a collaborator on npm for |
ping |
Hiya!
The latest version available through npm is v0.1.1. When attempting to use the library as given in the example in the README, v0.1.1 returns undefined.
I noticed that a lot of work had been done since then, and it looks like the latest version is 3.0.0.
As a workaround, I directly installed from this git repo (
npm install component/textarea-caret-position --save
).Could you please publish the latest version to npm?
The text was updated successfully, but these errors were encountered: