Breaking change in normalization of equals sign in query params #194
Description
We updated our version of normalize-url from 8.0 to 8.1 and our app broke due to a change in how query params with empty values are normalized:
This issue of whether or not to include = was addressed back in 2020 in issue #112. That issue was closed, seemingly with the understanding that adding the = was the intended, correct behavior.
I see that the recent change was intended to addres issue #193, but based on the comment (// Fix parameters that originally had no equals sign but got one added by URLSearchParams), it seems to have intentionally gone beyond that fix and introduced a breaking change in a minor revision, and without any configuration option to use the previous behavior.