use-query-params

• Resolves #67 by updating serialize-query-params to v0.2.0 (handles values like foo--1 -> foo: "-1" in object serializing)

• Aims to resolve #57 by running clean before building in prepublishOnly to get rid of old files that caused some people issues.

• Resolves #54 via #61 - concurrent updates with React Router will now work by looking at history.location instead of the provided location if available.

• Includes fix for initial values of SSR #58 #51

• Resolves #55 SSR with useQueryParams

• Resolves #46 by fixing the way memoization works on the setters returned from useQueryParam and useQueryParams. Also does automatic memoization on the paramConfigMap passed into useQueryParams to prevent it from re-generating new values and setters unnecessarily.

• Security vulnerabilities fixed and serialize-query-params bumped to 0.1.4

• Resolves #36 by adding in withUrlParams HOC and <QueryParams> render-props component

• Resolves #13 Next.js problems via #25 (SSR should work)
• Resolves #27 peer dependency was specified incorrectly

• Resolves #15 by switching to query-string 5
• Resolves #18 by adding esm build

• Resolves #11 by adjusting compilation settings to work with ES5

• Resolves #10: makes it so the query object returned from useQueryParams remains the same unless one of its values changes.

Breaking Changes

• No longer looks for a query object on location since the history package got rid of that in version 4.0.0. (#7)
• When encoding parameters that are not explicitly configured, defaults to converting them to strings.

Other Changes

• Refactored serialization logic into its own library serialize-query-params as per #4

Breaking Change

• Resolved issue: #1 (see #2)
  • Switches ArrayParam and NumericArrayParam to work with arr=a&arr=b&arr=c -> ['a', 'b', 'c'] style.
  • Renames old ArrayParam to DelimitedArrayParam, NumericArrayParam to DelimitedNumericArrayParam
  • Adds safe handling of array inputs to all parameters