Skip to content

fix: include full property path in TypeError for non-function member calls (issue #143)#147

Merged
Siubaak merged 2 commits into
masterfrom
claude/fix-issue-143-Z4efM
Apr 12, 2026
Merged

fix: include full property path in TypeError for non-function member calls (issue #143)#147
Siubaak merged 2 commits into
masterfrom
claude/fix-issue-143-Z4efM

Conversation

@Siubaak
Copy link
Copy Markdown
Owner

@Siubaak Siubaak commented Apr 12, 2026

When calling a non-function member like foo.bar(), the TypeError now reads
foo.bar is not a function instead of just bar is not a function, matching
the behavior of major JS engines (Node.js/browsers).

https://claude.ai/code/session_012YWgUtQyEApgN1EQAntvHo

claude added 2 commits April 9, 2026 05:11
…calls (issue #143)

When calling a non-function member like `foo.bar()`, the TypeError now reads
`foo.bar is not a function` instead of just `bar is not a function`, matching
the behavior of major JS engines (Node.js/browsers).

https://claude.ai/code/session_012YWgUtQyEApgN1EQAntvHo
)

When acorn reports "Unexpected token" for code like `async fetch('/url')` or
`foo bar`, rewrite the message to "Unexpected identifier 'fetch'" /
"Unexpected identifier 'bar'", matching Node.js/browser behavior.

https://claude.ai/code/session_012YWgUtQyEApgN1EQAntvHo
@Siubaak Siubaak merged commit 6214376 into master Apr 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants