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

Installation fails on node 10.10 #33

Closed
qrohlf opened this issue Sep 16, 2018 · 5 comments
Closed

Installation fails on node 10.10 #33

qrohlf opened this issue Sep 16, 2018 · 5 comments

Comments

@qrohlf
Copy link

qrohlf commented Sep 16, 2018

system: macOS High Sierra 10.13.6
node version: v10.10.0
yarn version: 1.9.4

When trying to install Postmark in my development environment, the install fails with the following message:

error upath@1.0.4: The engine "node" is incompatible with this module. Expected version ">=4 <=9".

It looks like one of your dependencies needs to be updated in order to support node 10. I'm going to skip integrating Postmark into my app for now, but I may come back to this next week and hit you with a PR if it's as simple as version-bumping one of your deps.

screen shot 2018-09-16 at 11 48 15 am

@ibalosh
Copy link
Contributor

ibalosh commented Sep 25, 2018

Hi @qrohlf

thank you for reporting this. We are doing a major update of the library, with typescript support. All of the dependencies and the code are being completely refactored.

It is going to be released in couple of weeks (hopefully next week).

We can check out the error then.

@qrohlf
Copy link
Author

qrohlf commented Sep 25, 2018 via email

@ibalosh
Copy link
Contributor

ibalosh commented Sep 26, 2018

sure, though I would advise to wait a week, the release coming out will make the current codebase obsolete, and it affects whole codebase.

Meanwhile, I took a quick look what could cause this and seem the resolution might be simple.
Check out the following:

enzymejs/enzyme#1637
anodynos/upath#20

removing lock files seem to be one of them.

Let me know how it goes

@qrohlf
Copy link
Author

qrohlf commented Oct 2, 2018

Removing my lock file did indeed fix my issue! Thanks for the help, should have done more searching before filing an issue.

@qrohlf qrohlf closed this as completed Oct 2, 2018
@ibalosh
Copy link
Contributor

ibalosh commented Oct 2, 2018

Hey!

no worries, glad things got sorted out and it works

Igor

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