Closed aryan02420 closed 1 month ago
I upgraded my local deno installation to 1.46, and now my project is broken. So it is not an actual bug with deno deploy.
vscode ➜ /workspaces/blog (main) $ deno --version
deno 1.46.3 (stable, release, x86_64-unknown-linux-gnu)
v8 12.9.202.5-rusty
typescript 5.5.2
vscode ➜ /workspaces/blog (main) $ deno task dev
Task dev deno run --allow-net --allow-read --allow-env --watch main.tsx --dev
Watcher Process started.
⚠️ Import assertions are deprecated. Use `with` keyword, instead of 'assert' keyword.
import emojis from "./all.json" assert { type: "json" };
at https://deno.land/x/emoji@0.3.0/emoji.ts:2:1
TypeError: Invalid URL: '/workspaces/blog/main.tsx'
at getSerialization (ext:deno_url/00_url.js:98:11)
at new URL (ext:deno_url/00_url.js:405:27)
at fromFileUrl (https://deno.land/std@0.193.0/path/posix.ts:460:36)
at configureBlog (https://deno.land/x/blog@0.7.0/blog.tsx:176:22)
at blog (https://deno.land/x/blog@0.7.0/blog.tsx:110:27)
at file:///workspaces/blog/main.tsx:6:1
error: Uncaught (in promise) Error: Cannot run blog from a remote URL.
throw new Error("Cannot run blog from a remote URL.");
^
at configureBlog (https://deno.land/x/blog@0.7.0/blog.tsx:180:11)
at blog (https://deno.land/x/blog@0.7.0/blog.tsx:110:27)
at file:///workspaces/blog/main.tsx:6:1
Watcher Process failed. Restarting on file change...
Does deno deploy let you choose what version of deno to use per project? If not, I think this is an oversight, since deploy always seems to use the latest version, which might have breaking changes causing projects using an older version to just stop working without any notice.
closing since this is not a direct bug in deno deploy
suggestion moved to #725
Hi thanks for opening this. We've rolled back the change that introduced this bug.
Problem description
projects using https://deno.land/x/blog@0.7.0/blog.tsx are returning 502 Gateway Error since October 4. Ryan's blog is affected too.
There has been no deployment or configuration change from my end. Locally the project is running just fine.
Steps to reproduce
Expected behavior
It should work on deno deploy too, just like it was working some days ago
Environment
My local environment which works fine
Possible solution
No response
Additional context
No response