Skip to content

Conversation

@jamestalmage
Copy link
Contributor

Due to NYC defaults, we were missing coverage on lib/test.js

I also added npm run coverage as a build target, which is for use
on developer machines. It launches a browser window with coverage
from the last run.

We no longer need NYC or coveralls as dev dependencies. tap handles
it all for us magically.

maintaining.md updated to reflect all these changes.

Also - I dropped coverage from the Windows tests. We don't need to make AppVeyor any slower.

Due to NYC defaults, we were missing coverage on lib/test.js

I also added `npm run coverage` as a build target, which is for use
on developer machines. It launches a browser window with coverage
from the last run.

We no longer need NYC as a dev dependency. `tap` handles it for us.

`maintaining.md` updated to reflect all these changes.
@sindresorhus sindresorhus changed the title Fixup coverage. Fix coverage Nov 24, 2015
jamestalmage added a commit that referenced this pull request Nov 24, 2015
Due to NYC defaults, we were missing coverage on lib/test.js

I also added `npm run coverage` as a build target, which is for use
on developer machines. It launches a browser window with coverage
from the last run.

We no longer need NYC as a dev dependency. `tap` handles it for us.

`maintaining.md` updated to reflect all these changes.
@sindresorhus
Copy link
Member

👍

@jamestalmage jamestalmage deleted the fix-coverage branch November 24, 2015 03:25
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