Skip to content

fix: allow to assets have absolute paths#12906

Closed
alexander-akait wants to merge 1 commit into
mainfrom
issue-12759
Closed

fix: allow to assets have absolute paths#12906
alexander-akait wants to merge 1 commit into
mainfrom
issue-12759

Conversation

@alexander-akait

Copy link
Copy Markdown
Member

What kind of change does this PR introduce?

bugfix, fixes #12759, I'm not sure if we should allow this

Did you add tests for your changes?

No, but I can you we accept this change

Does this PR introduce a breaking change?

No

What needs to be documented once your changes are merged?

No

@webpack-bot

Copy link
Copy Markdown
Contributor

For maintainers only:

  • This needs to be documented (issue in webpack/webpack.js.org will be filed when merged)
  • This needs to be backported to webpack 4 (issue will be created when merged)

@webpack-bot

Copy link
Copy Markdown
Contributor

@alexander-akait The most important CI builds failed. This way your PR can't be merged.

Please take a look at the CI results from azure (1 errors / 2 warnings) and appveyor (success) and fix these issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Target files on different drive than the output path cause invalid path and error is thrown

2 participants