Istanbul-lib-source-maps 1.0.2

[mourner]

mind submitting the corresponding pull to nyc; I think that's the only other place we need to update?

@bcoe I assume you referred to a dependency bump?

[coveralls]

Changes Unknown when pulling afb0ce2 on mourner:bump-source-maps into * on istanbuljs:master*.

[JaKXz]

Since it's a patch shouldn't it just be picked up automatically?

[mourner]

@JaKXz yes, but this should also in theory force an update if you do npm install, whereas without this you would need npm update. I think it doesn't hurt to update a patch dep if it contains a critical fix.

[JaKXz]

@mourner I agree - was just curious :)

[bcoe]

@JaKXz @mourner fun fact, we bundle-dependencies on this repo:

1. to improve install time (because our dependencies were getting pretty hefty).
2. it fixes some singleton related issues; by moving things into a sub-folder (you end up with two copies of libraries, rather than one when using npm 3).

Long story short, we need to explicitly bump dependencies on nyc.

[alexander-akait]

@JaKXz @bcoe some problems with install nyc@8.3.0 and istanbul-lib-source-maps@1.0.2
I am try

rm -r node_modules/nyc
npm cache clean
npm i nyc

I get nyc@8.3.0 but with istanbul-lib-source-maps@1.0.1, maybe someone from packages require istanbul-lib-source-maps@1.0.1 and we have istanbul-lib-source-maps: ^1.0.1, so I get not last version

[mourner]

@evilebottnawi there were no nyc release after this PR yet.

[alexander-akait]

@mourner understand it, and therefore I say that when you try to install nyc@8.3.0, i got istanbul-lib-source-maps@1.0.1, not istanbul-lib-source-maps@1.0.2

[mourner]

@evilebottnawi which is expected due to bundling of dependencies, as per #411 (comment)

[alexander-akait]

@mourner I should wait for a new version or it may be to solve?

[JaKXz]

@evilebottnawi I would suggest installing it from nyc@next to get the bug fix in and give it a spin :)

npm cache clear; npm i -D nyc@next