Skip to content
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

fixes issues with async #37

Merged
merged 1 commit into from
Oct 26, 2016
Merged

fixes issues with async #37

merged 1 commit into from
Oct 26, 2016

Conversation

gabrielcsapo
Copy link
Contributor

@gabrielcsapo gabrielcsapo commented Aug 14, 2016

adds async version to package.json

fixes #36

adds async version to package.json
:
@gabrielcsapo
Copy link
Contributor Author

@stackdot is anyone maintaining this repo?

@qrpike
Copy link
Contributor

qrpike commented Oct 25, 2016

Not actively, no

On October 21, 2016 at 4:48:21 PM, Gabriel Csapo (notifications@github.com)
wrote:

@stackdot https://github.com/stackdot is anyone maintaining this repo?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#37 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAo3HLa94VBqbulHmfErHpIAvl0cYLFvks5q2SUVgaJpZM4Jj_f9
.

@gabrielcsapo
Copy link
Contributor Author

@qrpike would you be interested in moving this under someone who would be actively managing issues?

@qrpike qrpike merged commit 2c6e47c into stackdot:master Oct 26, 2016
@qrpike
Copy link
Contributor

qrpike commented Oct 26, 2016

I would be willing to add you as a contributor if you like, giving you commit access.

@gabrielcsapo
Copy link
Contributor Author

@qrpike that would be great, could you provide NPM access as well?

@gabrielcsapo
Copy link
Contributor Author

gabrielcsapo commented Oct 27, 2016

@qrpike npm-username = gabrielcsapo

@qrpike
Copy link
Contributor

qrpike commented Oct 28, 2016

@gabrielcsapo seems you cant add access to a user npm module now, you have to create a npm org which costs $15/m. I guess just ping me when you need it pushed and I will push it for you. Would be even better if we could get the CI working again and have it auto publish through that only on successful changes.

@gabrielcsapo
Copy link
Contributor Author

@qrpike #40 this fixes the CI issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

issues with async 2.0
2 participants