Update path-browserify to v1.

[goto-bus-stop]

This version updates to the Node v10.3.0 API. This change is breaking,
because path methods now throw errors when called with arguments that are not
strings. Previously path.dirname, path.basename and path.extname did
not throw.

Change overview:

• Add path.parse and path.format.
• Add path.posix as an alias to path.
• Port tests from Node.js.

[billiegoose]

Ooooh! Ooooh! YAYAYAYAYAY!!!

[billiegoose]

Is there anything blocking this? I keep getting tripped by the lack of path.posix in Webpack's path module so this upgrade would be really nice.

[JakobJingleheimer]

@evilebottnawi could you merge this please?

[alexander-akait]

yep, in todo list, see on this in Monday, maybe we should update after stuff to for next major release

[alexander-akait]

@jshado1 unfortunately, we can't update, for webpack it is breaking change, also webpack@5 already doesn't add polyfills by default. Anyway i am open for idea how we can solve this

[goto-bus-stop]

@evilebottnawi there is another PR to update path-browserify to 0.0.1, which fixes the ReDOS vuln but doesn't introduce breaking changes: #89

[JakobJingleheimer]

@evilebottnawi shouldn't the arguments already be strings? I suppose it technically would be breaking if enforced now.

Sorry, I don't understand your comment about polyfills.

[alexander-akait]

@jshado1 webpack@5 doesn't add node polyfills by default, for webpack@4 it is breaking change

[sokra]

This library is deprecated and won't accept Pull Requests that include Breaking Changes or new Features. Only bugfixes are accepted.

[billiegoose]

the times, they are a-changin'