Skip to content

chore(coverage): Update instrumenter#101

Merged
eddywashere merged 3 commits intoreactstrap:masterfrom
TheSharpieOne:chore/update-instrumenter
Aug 18, 2016
Merged

chore(coverage): Update instrumenter#101
eddywashere merged 3 commits intoreactstrap:masterfrom
TheSharpieOne:chore/update-instrumenter

Conversation

@TheSharpieOne
Copy link
Copy Markdown
Member

Replace isparta with istambul since isparta is no longer maintained
See: https://github.com/douglasduteil/isparta
Istambul now support es2015/6.
(Also added cross-env to allow it to work on windows)

This PR is not a big deal, just some maintenance, though I did notice the coverage output was slightly more detailed with the babel istambul plugin this PR adds than the isparta loader it replaces.

Replace isparta with istambul since isparta is no longer maintained
See: https://github.com/douglasduteil/isparta
Istambul now support es2015/6.
(Also added cross-env to allow it to work on windows)
@TheSharpieOne TheSharpieOne force-pushed the chore/update-instrumenter branch from 4d07d5c to 64d148d Compare August 16, 2016 21:34
@coveralls
Copy link
Copy Markdown

Coverage Status

Changes Unknown when pulling 64d148d on TheSharpieOne:chore/update-instrumenter into * on reactstrap:master*.

1 similar comment
@coveralls
Copy link
Copy Markdown

Coverage Status

Changes Unknown when pulling 64d148d on TheSharpieOne:chore/update-instrumenter into * on reactstrap:master*.

Comment thread package.json Outdated
"dependencies": {
"babel-cli": "^6.11.4",
"classnames": "^2.2.3",
"cross-env": "^2.0.0",
Copy link
Copy Markdown
Member

@eddywashere eddywashere Aug 18, 2016

Choose a reason for hiding this comment

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

Can you move cross-env to devdeps? I know it's weird, but I was hoping to restrict dependencies to the core reactstrap library dependencies. I must have accidently added babel-cli to it.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

will do

@eddywashere
Copy link
Copy Markdown
Member

I think I should restrict tests to latest node version to avoid the double coverage reports.

@TheSharpieOne
Copy link
Copy Markdown
Member Author

Yeah, not too sure why it is not about to determine the changes to the coverage either and the branches are "**"... strange.

@coveralls
Copy link
Copy Markdown

coveralls commented Aug 18, 2016

Coverage Status

Coverage remained the same at 100.0% when pulling 27d32b9 on TheSharpieOne:chore/update-instrumenter into 18a2ef7 on reactstrap:master.

@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage remained the same at 100.0% when pulling 27d32b9 on TheSharpieOne:chore/update-instrumenter into 18a2ef7 on reactstrap:master.

1 similar comment
@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage remained the same at 100.0% when pulling 27d32b9 on TheSharpieOne:chore/update-instrumenter into 18a2ef7 on reactstrap:master.

Comment thread package.json
"react-dom": "^0.14.0 || ^15.0.0"
},
"devDependencies": {
"babel-cli": "^6.11.4",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

🙌 thanks!

@eddywashere eddywashere merged commit 3bf01b6 into reactstrap:master Aug 18, 2016
@TheSharpieOne TheSharpieOne deleted the chore/update-instrumenter branch August 18, 2016 01:15
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.

3 participants