Luke Page

@merceyz can you give any pointers on how to reproduce this situation? I need to define a yarn.lock file that has only v9 in it, bur yarn needs to be...

(I did look at the tests and setup, but it seems to be for simpler cases than what I am trying to reproduce)

Adding a explicit resolution also makes no difference. Editing the yarn.lock file manually and yarn just reverts the change - so looks like the only work-around is to not use...

sorry - a explicit resolution does work - I was missing that the resolution needs to be on the root package.json and there were no warnings about using it on...

@merceyz sorry you are right, I somehow missed it for months :(

I think this is because less actually marks up different parts of the selectors coming from different places.. so it tells chrome the first part of the selector comes from...

this bug is now in the chromium bugs: https://code.google.com/p/chromium/issues/detail?id=287382 note to self: could be solved by overriding the fileinfo before each path is output. also need to think about extends...

note: work-around from #1715 is to control and click on the property not the selector. note 2: chrome won't fix it so it would have to be addressed in less,...

Your use case sounds like what is discussed in #965 .. what do you think? Bearing in mind `&` is quite powerful already and we are bringing in `:extend()` in...

I like it. I prefer my suggestion of `&1` or @Soviut `&(1)`. I think probably that is my current winner.