-
Notifications
You must be signed in to change notification settings - Fork 24
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
Bump Deno #155
Bump Deno #155
Conversation
@lishaduck is attempting to deploy a commit to the Vercel Deno Team on Vercel. A member of the Team first needs to authorize it. |
Ping, @TooTallNate :) |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
I'm seeing a failure on the "dump" example endpoint. Looks like we'll need to start shipping the
|
Huh. That's weird. I don't have the "authorization required to deploy," yet it still deployed. ¯\_(ツ)_/¯ EDIT: Missed your last comment. |
Ok, when you run deno, you need to add the |
May I ask where those logs came from? Vercel? I'm not seeing how that's getting run. |
I had to manually approve it.
Yes, they were from the Vercel Logs tab. I think it's fine to have the lockfile, but we'll need to add it to the list of |
Ah. That makes sense.
Ok, I can add it. |
I think this handles it? It typechecks, at least.
You use PNPM, so you should tell corepack that. You also _seem_ to use prettier with single quotes for js files. Finally, pnpm/action-setup could get bumped with no changes. The latest version just enforces that packageManager stays in sync.
I'm not sure if there's a required amount of time before you bump Deno to ensure stability, but I didn't see anything, thus I went ahead and bumped it.