Closed venil7 closed 8 years ago
@venil7 yep we're trying to get in contact with the owner to update the npm package cc: @kylecesmat
I'm going to try to reach out to @asaf via Twitter
okay I've reached out to @asaf on Google+ and Twitter (sorry @asaf if you get the same message three times - wasn't sure which Google+ profile and Twitter profiles were correct)
@jpollard-cs @asaf @venil7 Yeah, we need to publish the latest to npm. If @asaf can make me a collaborator we could self-maintain this repo. Otherwise, we could rename this package on npm? (not ideal)
yeah let's give it a day or two then talk about alternatives - last time I used Twitter to get in touch with him it seemed to work
@kylecesmat You are already a collaborator on this repo. @asaf made you one after #9.
@ErezSha I think he means on npm...the builds/publishing are not automated
yes, and the version in npm is 1.0.2, but in the source code - 1.0.1, which is weird
Yeah - I'm going to make a tag on this repo today and if we don't hear from @asaf soon we'll make a new package on npm
redux-notifications
can be a good name for the new npm package
or just re-notify
I personally prefer redux-notifications
as it seems verbose. I'm weary to change the package name and break the version history. Any reason why we shouldn't?
Has a current version been published to npm? Has the name been changed?
@kylecesmat I have no strong feelings either way, but at this point I think we should publish a new npm package - no disrespect meant to @asaf, of course, but I think that would be a good solution until we hear from him
yes please publish under new name
Hey all! This issue can be closed, a new package has been created at redux-notifications
here - https://www.npmjs.com/package/redux-notifications
I'd love to help continue to support this project, if @asaf no longer has time to maintain then transferring ownership could be a great option?
cc: @jpollard-cs @venil7 @jcheroske @NameFILIP @ErezSha
whats in npm and what is here differ documentation does not match, etc....