-
Notifications
You must be signed in to change notification settings - Fork 3
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
Smoke test dependents #29
Conversation
t.plan(2) | ||
|
||
// Clone fully because we need git history for remark-git-contributors | ||
gitPullOrClone(url, cwd, { depth: Infinity }, (err) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice one!
const stdio = ['ignore', process.stderr, process.stderr, 'ipc'] | ||
const cli = path.join(__dirname, 'cli.js') | ||
|
||
cp.fork(cli, { cwd, stdio }).on('exit', function (code) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any special reason for .fork
than using .spawn
? Just curious.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I only chose it because it has a simpler API if it's JS you want to execute. Doesn't really matter.
This makes it easier to judge remark dependency updates (like the 4 PRs we have open now), which frequently have "to be safe" major bumps that don't actually affect us.