You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Require Module Support works well for the dojo AMD loading. It works even for relative path ./MyModule, but it fails for relative path to the parent dir ../MyModule - e.g. Ctrl + click does not work.
The text was updated successfully, but these errors were encountered:
Hey there, this seems to be still an issue. Relative paths of dependencies are resolved AGAINST the modulePath from the extension config and therefore pointing to a non-existing file paths.
This extension should not even work, are you sure it works if the path is not a parent path? I highly doubt it at this point as it is targeting 3-4 years old vscode APIs
This extension should not even work, are you sure it works if the path is not a parent path? I highly doubt it at this point as it is targeting 3-4 years old vscode APIs
I am using it on newest VSCode and all I need is to be able to ctrl-click-through to the depemndence module. So I fixed it locally in the ReferenceProvider.js by adding also the '../' pattern to the relative path test and it works as I needed.
The Require Module Support works well for the dojo AMD loading. It works even for relative path
./MyModule
, but it fails for relative path to the parent dir../MyModule
- e.g. Ctrl + click does not work.The text was updated successfully, but these errors were encountered: