Fix backslashes replacement.

[XhmikosR]

This resulted in backslashes in the URL entries on Windows.

R: @jeffposnick @addyosmani @gauntface

Fixes #771

[XhmikosR]

The AppVeyor failure seems unrelated to this change.

On a side note, I could add a test if you could give me some hints, i.e. which file the test should be, if I should just check for backslashes in entry.urls, etc.

[gauntface]

Thanks for this @XkhmikosR.

I'm waiting on a Windows machine to test this a little more. I'm largely curious to see if I can add some tests that "fake" windows files paths so we can test on linux for Window "style" support.

[XhmikosR]

@gauntface: you have AppVeyor so you can actually test Windows at any time https://www.appveyor.com/docs/how-to/rdp-to-build-worker/

It shouldn't be too hard to have a test for that. You could use https://nodejs.org/api/path.html#path_path_win32 or just hardcode the backslashes in a test case and just check if there are any in the output regardless of the OS.

[addyosmani]

@gauntface Change here LGTM, but I don't have access to our AppVeyor account to follow the windows test instructions @XhmikosR linked up to. If you get a chance can you add me or test it out? Would love to see if we can unblock twbs/bootstrap#23533

[XhmikosR]

Would be nice if we had a test to ensure this doesn't happen again in the future, though :)

[gauntface]

Gonna accept this merge and dig into a way of testing this better. Windows has been awful for a while and frankly I'm stumped on a sane way to test for it.

@addyosmani tried adding you to AppVeyor but no idea how the hell it's "teams" works

[gauntface]

Thanks again for this @XhmikosR - this will be cut in the release tomorrow.

[MikeyBeLike]

@gauntface thanks, can we get 2.0.1 published to npm too please

[jeffposnick]

Sorry, there were a few hiccups with the 2.0.1 release, but https://www.npmjs.com/package/workbox-build (and workbox-cli/workbox-webpack-plugin) are published.