René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"url: URLPattern.exec() result properties are not created in WebIDL order","articleBody":"### Version\n\nlatest main branch \n\n### Platform\n\n```text\n7.1.4-arch1-1\n```\n\n### Subsystem\n\nurl\n\n### What steps will reproduce the bug?\n\n```js  \n\n  const { URLPattern } = require('node:url');\n\n  const pattern = new URLPattern({ pathname: '/:value' });\n  const result = pattern.exec('https://example.com/test');\n\n  console.log(Object.keys(result));\n  console.log(Object.keys(result.pathname));\n  console.log(JSON.stringify(result.pathname));\n\n```\n\n### How often does it reproduce? Is there a required condition?\n\nEvery \n\n### What is the expected behavior? Why is that the expected behavior?\n\n```js\n  [\n    'hash',\n    'hostname',\n    'pathname',\n    'port',\n    'protocol',\n    'search',\n    'username'\n  ]\n\n  [ 'groups', 'input' ]\n\n  '{\"groups\":{\"value\":\"test\"},\"input\":\"/test\"}'\n```\n\n\n\n### What do you see instead?\n\n```js\n\n  [\n    'inputs',\n    'protocol',\n    'username',\n    'password',\n    'hostname',\n    'port',\n    'pathname',\n    'search',\n    'hash'\n  ]\n\n  [ 'input', 'groups' ]\n\n  '{\"input\":\"/test\",\"groups\":{\"value\":\"test\"}}'\n```\n\n### Additional information\n\n  Although direct property access is unaffected, property creation order is observable through:\n\n```js\n\n  Object.keys(result);\n  Object.values(result);\n  JSON.stringify(result);\n  ({ ...result });\n```\n\n  This makes Node.js behavior incompatible with browsers and WebIDL dictionary conversion semantics.","author":{"url":"https://github.com/Archkon","@type":"Person","name":"Archkon"},"datePublished":"2026-07-25T09:57:46Z","url":"https://github.com/nodejs/node/issues/64732"}