resolves #765 resolve custom cache directory to an absolute path

[mojavelinux]

No description provided.

[mojavelinux]

How's it look?

[mojavelinux]

@bcoe Anything else you want me to do?

[JaKXz]

Makes sense to me!

[bcoe]

@mojavelinux 👍 I apologize for taking a long time to land this, I've been facing a family tragedy, and have just been starting to do a tiny bit of open-source work again. I'll get a candidate release of this out the door for you soon, so you can test things out.

[bcoe]

@mojavelinux try npm i nyc@next this update should have your changes.

[mojavelinux]

No need to apologize. I completely understand. My heartfelt condolences to you and your family, from your family in open source. ❤️ Thank you for taking the time away from your family to review and merge this change.

[mojavelinux]

Fix confirmed!

[mojavelinux]

Thanks again!

While I now understand where nyc puts the cache by default, defining it explicitly in my package.json file makes me feel a lot more comfortable. I can now do that thanks to this fix:

  "nyc": {
    "cache": true,
    "cacheDir": "node_modules/.cache/nyc"
  }