-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
deno compile
/eszip does not follow redirects
#13704
Comments
The issue is because of the implicit import to
|
In my case deno also fails to import a script directly from GitHub using a raw link, regardless whether I specify the specify the branch name or the commit hash. Is this behavior intended? |
deno compile
failing with 1.19.0 with denoland/setup-deno@v1deno compile
/eszip does not follow redirects
There are other modules in the wild that are importing unversioned standard library modules which then redirect and then are not "compilable". for example {
"redirects": {
"https://deno.land/std/fmt/printf.ts": "https://deno.land/std@0.129.0/fmt/printf.ts",
"https://deno.land/std/path/mod.ts": "https://deno.land/std@0.129.0/path/mod.ts",
"https://deno.land/std/testing/asserts.ts": "https://deno.land/std@0.129.0/testing/asserts.ts"
}
} We really should fix this. |
Same problem here, we use the following command that fails with
We don't have any versions in {
"imports": {
"http": "https://deno.land/std/http/server.ts"
}
} because we rely on our {
"https://deno.land/std@0.132.0/http/server.ts": "10c3a7814666cdbabd6f9c18acdcc4593e222275a628280a4868881445fbb5bc",
} |
Since v1.19.0 was released, we're seeing a problem when running
deno compile
in Github Actions.See: https://github.com/ecadlabs/taqueria/runs/5234787765?check_suite_focus=true
We were using:
When I hardcode the version to 1.18.2 everything works fine:
https://github.com/ecadlabs/taqueria/runs/5236615612?check_suite_focus=true
The text was updated successfully, but these errors were encountered: