René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"repl: autocompletion after `new X.` targets `new X()`, not `X`","articleBody":"### Version\n\n25.0.0\n\n### Platform\n\n```text\n\n```\n\n### Subsystem\n\nrepl\n\n### What steps will reproduce the bug?\n\n```console\n\u003e class X { x = 1 }\nundefined\n\u003e X.Y = class Y { y = 2 }\n[class Y]\n\u003e new X. \u003c[Tab]\u003e \u003c[Tab]\u003e\nnew X.__proto__             new X.hasOwnProperty        new X.isPrototypeOf         new X.propertyIsEnumerable\nnew X.toLocaleString        new X.toString              new X.valueOf\n\nnew X.constructor\n\nnew X.x\n```\n\n### How often does it reproduce? Is there a required condition?\n\n\u0026nbsp;\n\n### What is the expected behavior? Why is that the expected behavior?\n\nProperty access has higher precedence than `new`, so this should autocomplete from the properties of `X`.\n\n### What do you see instead?\n\nAutocompletion from the properties of `new X()`. If X is not a constructor, offers nothing.\n\n### Additional information\n\nThe fact that the completer also triggers side-effects from calling the constructor in question is less than ideal, but this isn't the first issue on that front.","author":{"url":"https://github.com/Renegade334","@type":"Person","name":"Renegade334"},"datePublished":"2025-10-17T23:53:05.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/60306/node/issues/60306"}