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

support recent versions of the Fantasy Land specification #1

Merged
merged 1 commit into from
May 13, 2017

Conversation

davidchambers
Copy link
Contributor

I actually think it would be a good idea to deprecate this project and update the readme to suggest that people use Fluture instead. If you'd like to keep this project around, though, you're welcome to merge this pull request.

@Risto-Stevcev
Copy link
Owner

Thanks for the PR! 🙂

@Risto-Stevcev Risto-Stevcev merged commit e93540b into Risto-Stevcev:master May 13, 2017
@davidchambers davidchambers deleted the fantasy-land branch May 13, 2017 22:24
@davidchambers
Copy link
Contributor Author

Could you publish v2.0.0 so I can update plaid/deprecated-async-problem#31?

@Risto-Stevcev
Copy link
Owner

@davidchambers done 👍

@davidchambers
Copy link
Contributor Author

It looks as though you tagged an existing commit rather than updating "version" in package.json and pushing a new tagged commit. Perhaps as a result of this v2.0.0 is not available on npm:

$ npm view lazy-either versions
[ '1.0.0', '1.0.1', '1.0.2', '1.0.3' ]

I recommend xyz for avoiding such mishaps.

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.

2 participants