fix: resolve @import with absolute paths

[n1ru4l]

No description provided.

[jsf-clabot]

All committers have signed the CLA.

[codecov]

Codecov Report

Merging #201 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #201   +/-   ##
=======================================
  Coverage   97.93%   97.93%           
=======================================
  Files           7        7           
  Lines          97       97           
  Branches        8        9    +1     
=======================================
  Hits           95       95           
  Misses          2        2

Impacted Files	Coverage Δ
src/createWebpackLessPlugin.js	100% <100%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9ed895f...c1d0980. Read the comment docs.

[michael-ciniawsky]

Fixes #93

[michael-ciniawsky]

@n1ru4l Please add a test for this

[bebraw]

This needs a test.

I wonder if it would be better to fix loaderUtils.urlToRequest call (possible?). That would push complexity elsewhere, though. See https://github.com/webpack/loader-utils/blob/master/lib/urlToRequest.js .

[n1ru4l]

@bebraw Since the class is encapsulated inside a function this seems pretty hard to test for me :/. Any suggestions how I should proceed?
@bebraw I think this can be achieved by loaderUtils.urlToRequest(url, '')

[bebraw]

@n1ru4l Yeah, I think it would take some refactoring (extracting class?) to test this. But it's worth doing to avoid breaking the feature in the future.

[n1ru4l]

@bebraw I will try that!

[n1ru4l]

@bebraw I added a test that does not require any refactoring

[alexander-akait]

Seems good!