Skip to content

ci: build with deno v2 #2888

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

Merged
merged 16 commits into from
Aug 19, 2025
Merged

ci: build with deno v2 #2888

merged 16 commits into from
Aug 19, 2025

Conversation

mrstork
Copy link
Contributor

@mrstork mrstork commented Apr 30, 2025

Description

  • Used Deno v2.2.4 consistently across all CI workflows.
    After merging, Deno v1.46.3 will have to be replaced by Deno v2.2.4 in local development environments
  • Vendoring modules does not include type files by default, so those have been added to the vendor list
  • We aren't using vendor: true in deno.json as it prevents relative imports in edge
  • Moved deno.json into edge-runtime/ so that Deno v2 builds the vendor directory in that folder instead of the root
  • The package size failure is happening because the report compares the code in main to the code in this pull request, but deno vendor (which is used in main) is deprecated in Deno v2, thus results in a build failure. (See Deno v2 pkg size #3025 for package size report output)

@mrstork mrstork force-pushed the deno-v2 branch 2 times, most recently from 2b4320a to f45c2ed Compare July 16, 2025 20:47
@mrstork mrstork marked this pull request as ready for review August 5, 2025 17:39
@mrstork mrstork requested a review from a team as a code owner August 5, 2025 17:39
@mrstork mrstork merged commit 9d4ef4c into main Aug 19, 2025
29 of 30 checks passed
@mrstork mrstork deleted the deno-v2 branch August 19, 2025 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants