-
Notifications
You must be signed in to change notification settings - Fork 63
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
Relayer Loop #99
Relayer Loop #99
Conversation
85e06e3
to
787a14a
Compare
787a14a
to
1a137a3
Compare
}; | ||
|
||
run(options, logger); | ||
await run(options, logger); |
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.
no need for await
here but it doesn't hurt
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 guess not, but if I neither await
nor return the Promise, then if the caller tries await
, it will not wait for the final promise with the heart of the work.
I guess we don't do it that way here, but it is a habit after a few gotchas with unawaited promises
wasmd, | ||
} from './testutils.spec'; | ||
} from './testutils'; |
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.
@ethanfrey This filename had a .spec
in it to group it with test files, eg so that it's filtered out of the files published to npm.
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.
When I removed the unit tests there and left it as spec, ava complained (errored).
Maybe just add this file to the npmignore file?
Most of #12
Part 1 of #89
--once
flag)Follow up PR: