useRelativePath broken after update from 1.1.6 to 1.1.9

[lukaszsamson]

With the following options

options: {
              emitFile: false,
              name: '[name].[ext]',
              publicPath: 'assets/',
              useRelativePath: true
            }

and requiring img/path/to/file.png

In 1.1.6 the resulting URL is correct
assets/img/path/to/file.png
In 1.1.9 its
assets/file.png

[alexander-akait]

@lukaszsamson can you create minimum reproducible test repo?

[lukaszsamson]

I don't have a minimum repro, but I tested it a bit more and the regression was introduced in 1.1.8

[alexander-akait]

@lukaszsamson without test repo it is hard to indicate problem place

[kernle32dll]

@lukaszsamson maybe a cause of #246? At least I stumbled across this yesterday and it seems oddly similar to your problem.

[alexander-akait]

@kernle32dll right now we fix options how they should work, somebody can have invalid path configuration using bugs

[zemadz]

I've created a minimum repo to demonstrate this issue: https://github.com/zemadz/file-loader-relative-path-minimum-repro

There are two branches:

• master (with file-loader@1.1.8)
• working (with file-loader@1.1.7)

Run npm run build and see the output at build/js/index.js or npm test to investigate the different behaviors.

[lukaszsamson]

#260 does not fix the issue

[michael-ciniawsky]

Released in v1.1.11 🎉

[ossinkine]

@lukaszsamson I've faced with the same issue. Since #260 does not fix the issue how did you fix this?

[alexander-akait]

@ossinkine useRelativePath option was removed in major release

[lukaszsamson]

@ossinkine I stopped using this plugin in my config