fix: extract relative path

[SASUKE40]

Fixes #250

[codecov]

Codecov Report

Merging #262 into master will increase coverage by 0.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #262      +/-   ##
==========================================
+ Coverage   92.42%   92.47%   +0.04%     
==========================================
  Files          10       10              
  Lines         317      319       +2     
  Branches      113      112       -1     
==========================================
+ Hits          293      295       +2     
  Misses         23       23              
  Partials        1        1              

Impacted Files	Coverage Δ
src/index.js	98.97% <100.00%> (+0.02%)	⬆️

---

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 df71f37...14b12b6. Read the comment docs.

[egoist]

🎉 This PR is included in version 2.8.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[calebeby]

This should have been released as a major version because this is a breaking change for this use case:

postcss({extract: 'dist/style.css'})

In 2.8.1 this correctly placed the file in the relative location of dist/style.css. In 2.8.2 this does not place the file there

[SASUKE40]

related #266

[SASUKE40]

This should have been released as a major version because this is a breaking change for this use case:

postcss({extract: 'dist/style.css'})

In 2.8.1 this correctly placed the file in the relative location of dist/style.css. In 2.8.2 this does not place the file there

I have released two version:

• v2.9.0@latest for rollup v1 and v2(it prints some warning messages when using custom extract).
• v3.0.0@next only for rollup v2(not allow generate files outside bundle directory).