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
Missing redirect => broken import #18528
Comments
FYI we're trying to see if an intentionally broken artifact could fix the current state but I am worried if you fix this bug instead such artifact will suddenly break too ... if you think you are going to fix this please let me know but if you think that's just fine as it is then we should be good if the |
P.S. I can confirm the artifact works via |
I don't expect this to change, it's a known limitation of the default files. You have several options, however:
|
unpkg simply redirects to the entry point which works as expected so this seems to be more a choice (avoid redirect) than a limitation but I am OK with this answer if it means we can trust current |
P.S. |
Description
This url https://cdn.jsdelivr.net/npm/@pyscript/core correctly understands the original file:
however, the original file would import from
/npm/@pyscript/core@0.1.15/
while currently your served file let the browser think that a/npm/@pyscript/dist
project exists, which is not the case.In short, if that
/core
end points serves this content:the whole package breaks because
/core
is considered the current file while/core/index.js
is the actual base URL reference.Affected jsDelivr links
https://cdn.jsdelivr.net/npm/@pyscript/core
Response headers
not relevant
Information
not relevant
Requisites
Additional content
The only way to fix this right now is via
importmap
that catches all@pyscript/dist
prefixes and redirect these to@pyscript/core/dist
but that seems unfortunate, as workaround, and it prevents us from publishing in the future a@pyscript/dist
module with anything else different from core.The text was updated successfully, but these errors were encountered: