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

Warn if changes to package.json and not yarn.lock #102

Merged
merged 2 commits into from
Jan 18, 2017

Conversation

macklinu
Copy link
Member

@macklinu macklinu commented Jan 17, 2017

#trivial

Based on jestjs/jest#2508

This would have applied to #101 (discovered when I merged master into and ran yarn install on #99).

@macklinu
Copy link
Member Author

macklinu commented Jan 17, 2017

I force pushed up an amended commit that would fix the build, but GitHub doesn't seem to be aware of that amended commit yet. Will check back later.

EDIT: nevermind, it's showing up now!

@macklinu macklinu force-pushed the package-json-yarn-lock-warning branch from 96242d8 to c06c20c Compare January 17, 2017 20:57
@@ -1,5 +1,6 @@
// import { danger, warn } from "danger"
import fs from "fs"
import includes from "lodash.includes"
Copy link
Member Author

Choose a reason for hiding this comment

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

Do we need to worry about Node 4 support, or should I just use the built-in Array.prototype.includes() function here?

@macklinu
Copy link
Member Author

It looks like there are Appveyor builds queueing up too. I logged in with GitHub but don't see a button to cancel old builds.

image

@orta
Copy link
Member

orta commented Jan 17, 2017

Yeah, I've been seeing it on other repos - I'm cool with merging without it

and yeah, I don't think TS backports the includes function, so best use the loads version IMO

@orta
Copy link
Member

orta commented Jan 18, 2017

👍

@orta orta merged commit e117d03 into master Jan 18, 2017
@orta orta deleted the package-json-yarn-lock-warning branch January 18, 2017 22:10
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