- v2.6.1Latest
- v2.6.0
- v2.5.6
- v2.5.5
- v2.5.4
- v2.5.3
- v2.5.2
- v2.5.1
- v2.5.0
- v2.4.4
- v2.4.3
- v2.4.2
- v2.4.1
- v2.4.0
- v2.3.1
- v2.3.0
- v2.2.0
- v2.1.1
- v2.1.0
- v2.0.1
- v2.0.0
- v1.5.3
- v1.5.2
- v1.5.1
- v1.5.0
- v1.4.0
- v1.3.0
- v1.2.0
- v1.1.2
- 1.1.1
- 1.1.0
- 1.0.6
- 1.0.5
- 1.0.4
- 1.0.3
- 1.0.2
- 1.0.1
- 1.0.0
- 0.16.2
- 0.16.1
- 0.16.0
- 0.15.7
- 0.15.6
- 0.15.5
- 0.15.4
- 0.15.3
- 0.15.2
- 0.15.1
- 0.15.0
- 0.14.0
- 0.13.1
- 0.13.0
- 0.12.2
- 0.12.1
- 0.12.0
- 0.11.1
- 0.10.1
- 0.10.0
- 0.9.2
- 0.9.1
- 0.9.0
- 0.8.1
- 0.8.0
- 0.7.0
- 0.6.0
- 0.5.3
- 0.5.2
- 0.5.1
- 0.5.0
- 0.4.0
- 0.3.0
- 0.2.2
- 0.2.1
- 0.2.0
- 0.1.3
Init
Start Deno projects in Visual Studio Code a little faster with deno-init
, a small executable that scaffolds a Deno project structure for you.
Select a language (js/ts), entrypoint and optionally a debug configuration.
Please note this module’s API is not yet stable and there may be breaking changes on 0.x
version increments.
Prerequisites
- Deno
- Visual Studio Code
- Deno Language Extension for Visual Studio Code
Installation
deno install --allow-read --allow-write -n deno-init https://deno.land/x/init/init.ts
Basic Usage
deno-init
When run without any options deno-init
will ask for:
- JavaScript or TypeScript (default TypeScript)
- entrypoint (default
mod.ts
) - dependency entrypoint (default
deps.ts
) - debug configuration file for debugging Deno in Visual Studio Code (default:
y
).
Available Options
If you simply want to use all the default values you can pass --yes
or -y
. Note that deno-init
will not overwrite anything by default in case you already made some of the files/directories:
deno-init -y
In case you explicitly want to overwrite existing files you can pass --force
or -f
:
deno-init -f
When you run the command with --name
or -n
the script will also create a project directory with the given name and then will add the files into it.
deno-init -n myDenoProject