You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor: simplify Deno support to match other package managers
- deno now follows the same pattern as npm/yarn/pnpm/bun
- unified install step handles all package managers
- support npm dependencies in hybrid Deno projects via deno install
- use package-manager input for Deno version (e.g., [email protected])
Copy file name to clipboardExpand all lines: action.yml
+34-21Lines changed: 34 additions & 21 deletions
Original file line number
Diff line number
Diff line change
@@ -9,21 +9,13 @@ inputs:
9
9
required: false
10
10
default: "22"
11
11
package-manager:
12
-
description: "You may specify your preferred package manager (one of `npm | yarn | pnpm | bun` and an optional `@<version>` tag). Otherwise, the package manager will be automatically detected."
12
+
description: "You may specify your preferred package manager (one of `npm | yarn | pnpm | bun | deno` and an optional `@<version>` tag). Otherwise, the package manager will be automatically detected."
13
13
required: false
14
14
default: ""
15
15
path:
16
16
description: "Path of the directory containing your site"
17
17
required: false
18
18
default: "."
19
-
deno-version:
20
-
description: "The Deno version to use when deno.json/deno.jsonc/deno.lock exists"
21
-
required: false
22
-
default: "1.x"
23
-
deno-setup-task:
24
-
description: "Name of the optional Deno task to run before build (will be skipped if undefined)"
0 commit comments