-
-
Notifications
You must be signed in to change notification settings - Fork 83
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
Incorrect resolving for scoped import maps #33
Comments
This is actually working as designed, and is a bug in jspm itself rather (and SystemJS, with the PR for SystemJS currently at systemjs/systemjs#1975). The import maps specification changed such that scopes are resolved relative to the import map base, instead of the scope itself. |
Thanks for your answer. Is there any issue added in jspm related to this matter? |
See jspm/jspm-cli#2493. |
Thanks! |
Sure, this fix is now released in 2.0.0-beta.7. That should resolve this, but please let me know if you have further issues at all. |
I just tested it and it works. Thanks once again! |
Hello, @guybedford,
The last es-module-shims version fails to identify the scoped import maps.
This is a piece of the import map that I use (generated with jspm):
I investigated a little bit and I think the problem's root is in
parseImportMap
:es-module-shims/src/common.js
Line 144 in c2ad855
I think this line should be:
baseUrl
for scoped packages should be the resolved url of their 'parent'.Please let me know if you think I identified correctly the cause of the issue and I'll come up with a pull request.
Thanks!
The text was updated successfully, but these errors were encountered: