Closed noahsw closed 7 years ago
Thanks @noahsw ! I will look at it, but it looks like es6 is not fully supported, right ?
You referring to #11 ? That certainly is strange. I didn't realize only certain types of exports would be supported. Not even sure where to start with that one. Is it a Meteor issue? An ecmascript package issue? I'd expect a compile-time error at the very least.
Fixed by meteor-coverage v1.1.3
. Since the v~0.9
, we have some ES6 code and node code that uses node >v0.11
.
Meteor apps on version 1.3
uses node 0.10
, so it can just fail.
This is after making tweaks to
Conf.js
to get the exports to work properly (See issue #11).When app is run with
COVERAGE=1
, all the logging seems to suggest the app is being instrumented properly. However, I can't open the app onhttp://localhost:3000
even though it saysApp running at http://localhost:3000
. The browser simply never gets a response.If I run with
COVERAGE=0
, my app loads fine.Expected Behavior
I expect the app to load and the coverage to run when browsing to localhost.
Current Behavior
Steps to Reproduce (for bugs)
COVERAGE=0 COVERAGE_VERBOSE=1 COVERAGE_APP_FOLDER=${PWD/#$HOME/~}/ meteor
Context
Your Environment