serut
serut
Small changes as it failed to build on my side (and I use nginxinc/nginx-unprivileged): ``` FROM debian:stable AS builder ARG version='1.21.6' ARG build_dir="/usr/share/tmp" ARG nginx_module_dir="/usr/local/nginx/modules/" # Setup RUN apt-get update...
I don't think meteor-coverage is still working, as I can see the test from the package are not working anymore : ``` $ meteor npm install ... $ meteor npm...
It would be cool if that fixes meteor-coverage tests
I assume lmieulet:[email protected] uses Meteor 1.8, whereas 4.0.0 uses the latest one. So it can be related to the update of node
> Hm but how can this change lead to empty coverage? Isn't it relying on Istanbul? Yes most of the job is packaged with babel / istanbul. But the remap...
It looks way better without this second call : https://github.com/serut/meteor-coverage/blob/da59c18331807069e49465e27b1c3e072159f467/server/report/report-remap.js#L59 I've published lmieulet:[email protected], can you try it? The HTML report does not look functionnal, but text report OK. Let's see...
Ok so you don't have lcov and or html coverage report ? May I ask you a reproductible env ?
No time yet to work on this
I don't think I can fix this. Maybe the variable `process.env.PWD` is not the right one to use with meteor-coverage?
I think that's always the case when you run `babel-plugin-istanbul` or any other coverage library. I use the source map after to retrieve the correct path