I want to start making things a bit more durable, so I thought I would start with the minimal template. You should be able to run deno task ok with this, after bootstrapping a project.
Sadly it seems like the CLI always pulls the template from github, even when I try running it directly via deno run -A netzo/lib/cli/netzo.ts init. This of course prevents me from properly testing this locally.
My next PR will be to fix this limitation and add a test that runs as part of CI. The test should:
bootstrap a project with deno run -A ./lib/cli/netzo.ts init
cd into the project
run deno task ok
This will at least ensure that we can use the CLI to make a new project and start it without errors.
A fun variation on this (for the PR after the above plan) would be to add a new route to the template (programmatically), and then bootstrap the project and try visiting the new route. This would assert that the CLI can initialize projects with local changes to the template.
I want to start making things a bit more durable, so I thought I would start with the
minimaltemplate. You should be able to rundeno task okwith this, after bootstrapping a project.Sadly it seems like the CLI always pulls the template from github, even when I try running it directly via
deno run -A netzo/lib/cli/netzo.ts init. This of course prevents me from properly testing this locally.My next PR will be to fix this limitation and add a test that runs as part of CI. The test should:
deno run -A ./lib/cli/netzo.ts initdeno task okThis will at least ensure that we can use the CLI to make a new project and start it without errors.
A fun variation on this (for the PR after the above plan) would be to add a new route to the template (programmatically), and then bootstrap the project and try visiting the new route. This would assert that the CLI can initialize projects with local changes to the template.