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

yarn install fails for node > 4.0.0 #4

Open
hayeah opened this issue Jul 28, 2017 · 4 comments
Open

yarn install fails for node > 4.0.0 #4

hayeah opened this issue Jul 28, 2017 · 4 comments
Assignees

Comments

@hayeah
Copy link

hayeah commented Jul 28, 2017

ipld 0.6 locks the node version to ^4.0.0. It is required by transmute-framework.

https://github.com/transmute-industries/transmute-framework/blob/b14becb8f42380870f467246d4d920289e8945c5/package.json#L75

A work around for now is to use yarn, and tell it to ignore node version constraint:

yarn install --ignore-engines

The original ipld library seems to have migrated to a new package, which is compatible with node >=4.0.0

https://github.com/ipld/js-ipld-dag-cbor

Not sure whether this is a compatible package though.

@OR13
Copy link
Member

OR13 commented Jul 28, 2017

@hayeah thanks for reporting this issue and especially the workaround!

I will give migrating to the new package a shot and report findings.

The framework only uses marshal and unmarshal so it should be simple to upgrade.

@OR13
Copy link
Member

OR13 commented Jul 28, 2017

@hayeah This pr upgrades the ipld package... I'm not a huge fan of the new package name... but i am a big fan of being up to date. thanks!

transmute-industries/transmute-framework#76

@OR13 OR13 self-assigned this Jul 29, 2017
@OR13
Copy link
Member

OR13 commented Aug 4, 2017

I'm closing this as I believe the PR resolved this issue.

@OR13 OR13 closed this as completed Aug 4, 2017
@OR13 OR13 reopened this Aug 11, 2017
@OR13
Copy link
Member

OR13 commented Aug 11, 2017

This issue has been reproduced, the issue is now with

Unsupported engine for "got@5.7.1"

Having trouble determining which package is importing this old busted package.

Its times like these I love node...

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

No branches or pull requests

2 participants