Remove nyc as a global dependency

[roschaefer]

Local installation over global installation, no? 🤔

@appinteractive I don't see the difference between test and test:coverage. On current develop branch the two results look like the same.

[appinteractive]

The results yes but did you get the same results in the coverage folder?

The local installation of nyc does not work for me at all.

[roschaefer]

OK, so test:coverage creates the file lcov.info in coverage/? That does not work locally on my machine. The tests behave as expected though.

I guess I have to research some more on how to chain scripts in package.json. I find the current package.json quite confusing and would like to clean it up a little.

[appinteractive]

Yeah we need some cleanup indeed!

[appinteractive]

I don't know why but intalling nyc localy always throws this:

Even in yarn dev

[ghost]

@appinteractive just found this: npm/npmlog#48

seems nuking node_modules works in some cases. In others there are dependency conflicts where packages require different versions of gauge where older versions do not have isEnabled as a function.

[appinteractive]

@sebako86 funny I just was there and saw your reference (two min before) ^^
Sadly that does not help in my case.

[appinteractive]

As we are in the process of upgrading packages for feathers v3 this might solve a he issue.

[appinteractive]

Works for everyone except me so I will merge it and still install it for me globally for now.