-
Notifications
You must be signed in to change notification settings - Fork 5
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
Error when trying to jump to dependency #212
Comments
Thanks for reporting the issue! I assume the The parsed To help me identify the cause better, you can supply debug info via:
Any additional info is appreciated. Thanks in advance! |
Sent you an email with the information. |
Thanks!x |
looks like resolved location is something |
Thanks for the details. Will look into it further tonight. The culprit is the fact that your baseUrl has a leading slash. According to the requirejs spec, that has special resolution logic. Though I think there's room for your baseUrl to become I'll try to get in a fix tonight and have that released to package control so that you can update Dependents tomorrow morning. Thanks again. |
RequireJS would resolve that about the html page referencing loading the app. Since that context is missing, we'll fix the resolution directory to avoid duplicating the baseUrl in the resolved filepath. Ref dependents/Dependents#212
* ES6 correctly parses JSX and ES7 source files using Babylon * AMD fix for baseUrls with a leading slash. * Fixes #212
That was precisely it. I pushed the fix all the way through and submitted it for a package control release (should be available as a Dependents package update in an hour). Please let me know if the fix doesn't resolve your issue. I imagine this bug would have also broken the Find Dependents feature. Thanks a ton for reporting it. Please feel free to report any additional bugs or pain points. |
FYI, this bug fix has been propagated to Find Dependents. The other features (view tree and find entry points) will get this fix shortly. Thanks again for reporting! |
The text was updated successfully, but these errors were encountered: