[remote functions] remote query hash key is not stable for object keys in different orders.

[jaycejonestrinityonline]

Describe the bug

getFoo({ foo: 1, bar:2 }) and getFoo({ bar:2, foo: 1 }) do no produce the same hash leading to additional request being made or stale data in the case of getFoo(...).refresh().

Reproduction

https://stackblitz.com/edit/sveltejs-kit-template-default-vixwlscz?file=src%2Froutes%2F%2Bpage.svelte

on index page, notice demoQuery is loaded twice. click "click me" and notice only 1 remote query is refreshed

Logs

N/A

System Info

System:
    OS: Linux 6.6 Ubuntu 22.04.5 LTS 22.04.5 LTS (Jammy Jellyfish)
    CPU: (32) x64 13th Gen Intel(R) Core(TM) i9-13900
    Memory: 21.93 GB / 31.19 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 20.18.0 - /home/jayce/.nvm/versions/node/v20.18.0/bin/node
    npm: 10.8.2 - /home/jayce/.nvm/versions/node/v20.18.0/bin/npm
    pnpm: 10.18.0 - /home/jayce/.local/share/pnpm/pnpm
    bun: 1.1.15 - /mnt/c/Users/jjones/AppData/Roaming/npm/bun

Severity

serious, but I can work around it

Additional Information

No response

[elliott-with-the-longest-name-on-github]

We've talked about this at some point, and I can't remember where we landed. The problem is, object keys are actually ordered in JavaScript, so we have two choices:

• Sort objects recursively before serializing them, which is both expensive and will change the key order when they're deserialized
• Don't sort objects, which is free, at the cost of this unexpected behavior

I think in the past we'd decided to leave it as-is... @dummdidumm do you remember when this came up?

[jaycejonestrinityonline]

I understand object keys are technically ordered in modern js. My problem as is there is no way to type that to enforce consist order across use leading to over fetching and in my case data not refreshing.

Coming from tools like tanstack query where object keys are sorted I sort of took it for granted that same would happen here.

To point 1 you technically only need to sort when generating the key/hash the request could retain its order in theory.

One option would be let the user define a hashing function so they decide which issue they want to deal with. Personally my query request are never massive and having data fail to refresh is nearly enough to deter me from remote queries all together.

Sorry for formatting issues/typos on mobile at the moment

[Conduitry]

It came up before in #14906 (where the underlying issue is being concealed when using some validation libraries but not others). I'm in favor of not normalizing, personally.