8000 Disable esModuleInterop to restore VSCode monkeypatching by machty · Pull Request #858 · typed-ember/glint · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Disable esModuleInterop to restore VSCode monkeypatching #858

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Mar 27, 2025

Conversation

machty
Copy link
Contributor
@machty machty commented Mar 27, 2025
  1. Restore value to esModuleInterop=false so that fs.readFileSync = ... monkeypatch continues to work (with esModuleInterop=true, fs = require(...) becomes fs = _importStar(require(...) and you end up getting a "setting read-only property" error)
  2. Remove the try catch wrapping to surface these issues in our test suite (and in the wild as more people start trying out the alpha)

I don't know exactly which specific features this restores; it didn't fix the auto-complete issues I'm seeing but I believe some cases of "Go to Definition" with .gts files have been fixed.

8000
@machty machty changed the title Disable moduleInterop to restore VSCode monkeypatching Disable esModuleInterop to restore VSCode monkeypatching Mar 27, 2025
@NullVoxPopuli NullVoxPopuli added the bug Something isn't working label Mar 27, 2025
@NullVoxPopuli NullVoxPopuli merged commit b3b84fd into main Mar 27, 2025
4 checks passed
@NullVoxPopuli NullVoxPopuli deleted the restore-vscode-hacks branch March 27, 2025 18:53
@github-actions github-actions bot mentioned this pull request Mar 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
0