+ should be decoded to +, not to a space

[lebed2045]

Found a bug in my our project because of this lib https://www.npmjs.com/package/query-string depends on your library which basically incompatible with industry standard https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify

[Anusien]

See this comment. I don't think decode-uri-component is responsible for this.

[adguy360]

See this comment. I don't think decode-uri-component is responsible for this.

Of course it's responsible https://github.com/SamVerschueren/decode-uri-component/blob/main/index.js#L86, and it also breaks query-string.

Not sure how this pkg was ever a "better decodeURIComponent" (as it claims to be) but you should definitely avoid using it, and better avoid query-string as well if you can - native solutions are better and certainly better maintained.

If you have query-string as a nested dependency and need some simple sketchy fix, you can encodeURIComponent your value before passing it to query-string's stringify. This will "hide" the + sign from this pkg's nasty parsing logic.

[SamVerschueren]

Not sure how this pkg was ever a "better decodeURIComponent" (as it claims to be) but you should definitely avoid using it

Try decoding %7B%ab%%7C%de%%7D with the native decodeURIComponent and then come back with some useful feedback.

When I created this package (which was specifically made for query-string if I'm not mistaken), it seemed like the right thing to do. Which might be the case for query string values, but not for other parts of the URI. So I think it makes sense to remove it in this package.

cc @sindresorhus do you think that makes sense?

[sindresorhus]

Yes, the special + handling is a query string only thing, not for all URL components.

https://stackoverflow.com/a/6855723/64949

[SamVerschueren]

Ok, I'll remove the + handling and publish a new breaking change.

[SamVerschueren]

Released as 0.3.0.