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 Node >=v14 #43

Closed
stewart-lore opened this issue Jun 14, 2022 · 3 comments · Fixed by #50
Closed

Support Node >=v14 #43

stewart-lore opened this issue Jun 14, 2022 · 3 comments · Fixed by #50

Comments

@stewart-lore
Copy link

stewart-lore commented Jun 14, 2022

Most apps that will use seaport-js will be webapp clients. It doesn't make sense to enforce the latest node version when node is not used on the client.

I'm requesting that you downgrade the seaport-js node requirement to 14, ie >=v14.19.1 or just remove this restriction altogether.

The reason I'm asking is because I'm up-taking seaport on my client app which is served by a Node 14 server-- it's turning out to be a challenging upgrade. Since the seaport protocol was just released, it is time sensitive for my app to upgrade before you disable wyvern.

Thanks.

@plondon
Copy link

plondon commented Jun 15, 2022

We're also in the process of integrating seaport for https://github.com/blockchain/blockchain-wallet-v4-frontend and would also prefer >= node 14, or at the least unpin the patch version.

@sunwrobert
Copy link
Collaborator

Published 1.0.2

@stewart-lore
Copy link
Author

@sunwrobert Thanks!

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 a pull request may close this issue.

3 participants