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

chore: working builds for Appveyor, use Node.js 8 and 10 #195

Merged
merged 9 commits into from
Jan 30, 2019
Merged

chore: working builds for Appveyor, use Node.js 8 and 10 #195

merged 9 commits into from
Jan 30, 2019

Conversation

DanielRuf
Copy link

@DanielRuf DanielRuf commented May 9, 2018

Description

This PR tries to fix the failing Appveyor Windows builds.

@cjpatoilo cjpatoilo self-assigned this May 9, 2018
@DanielRuf DanielRuf changed the title chore: update Appveyor config for building on Windows with libvips chore: working builds for Appveyor, use Node.js 8 and 10 May 9, 2018
@cjpatoilo cjpatoilo assigned DanielRuf and unassigned cjpatoilo May 9, 2018
@cjpatoilo cjpatoilo self-requested a review May 9, 2018 12:26
@DanielRuf
Copy link
Author

Related: nodejs/node#20325

@DanielRuf
Copy link
Author

Mh, I guess we can mark this as WIP until it is fixed in the dependencies and Node.js.

@DanielRuf
Copy link
Author

Bump.

@cjpatoilo cjpatoilo merged commit 92cd1ff into milligram:master Jan 30, 2019
@cjpatoilo
Copy link
Member

@DanielRuf Good call! 🚀

@DanielRuf DanielRuf deleted the chore/update-appveyor-config branch March 17, 2019 19:16
}
},
"resolutions": {
"natives": "1.1.3"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@DanielRuf please, help me to understand more about this. Could you explain better?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is for yarn to use the natives-version instead of a newer / older one as there is an issue with old Node versions like Node 8 - I think it was the compatibility / some crash.

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