This easily does support query params as it is today.

[omerp-explorium]

const pathname = "/users/:id/profile\\?{first=:first}{&second=:second}";

const matcher = match(pathname);
const parser = compile(pathname);

matcher("/users/5/profile") // works
parser({ id: "5", first: "4" }) // yields /users/5/profile?first=first
parser({ id: "5", first: "4", second: "3" }) // yields /users/5/profile?first=first&second=3

/// The drawback:
parser({ id: "5", second: "3" }) // yields /users/5/profile?&second=3
// But we could simply do:
parser({ id: "5", second: "3" }).replace(/\?\&/g, "?")

[blakeembrey]

I do not recommend this and recommend using something like URLSearchParams instead. Query parameters aren't ordered, it should be valid to write second=3&first=first.

There's also the issue of the delimiter needing to be changed to match different sections. Currently it stops of /, but you'd need to also stop of ?, &, and maybe even # if it's used on the front-end.