-
Notifications
You must be signed in to change notification settings - Fork 289
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
EDITOR: Cannot resolve import paths in some cases #1747
Comments
Yes, we should assume #1477 is dead in the water and steal pieces from it that are useful or mergeable. |
I've seen this error in the past as well when I updated the import resolution. However, I believe I wasn't able to fix this because from what I understand this is an edge case of the way we interact with and provide model data to monaco. |
Update: |
Update: |
TypeScript support will be available on the stable version via #1216. In some cases, monaco cannot resolve the import paths. This is just a problem with the script editor UI. It does not affect anything else. It may be fixed by #1477, but I don't think that fix can be merged easily.
MRE:
lib.ts
test.ts
Screenshot:
With this case (use an absolute path), the player can work around by using a relative path (
./lib
instead of/lib
).I'll use this issue to keep track of the problem and potential fixes. Other reports can be marked "duplicate" and linked back to here.
Test suite:
test suite for editor.gz
The text was updated successfully, but these errors were encountered: