Why
fedify init creates runnable apps, but generated projects do not have a standard local smoke-test command. A small generated task that starts the app and verifies a local actor lookup would help new users and would give contributors a clearer way to validate scaffold changes.
Scope
Add a smoke-test task to generated projects from @fedify/init. The task should be practical across supported package managers and should check the generated actor endpoint with fedify lookup or an equivalent local request.
This will likely touch task generation in packages/init/src/action/, framework descriptions in packages/init/src/webframeworks/, and tests under packages/init/src/test/. Keep the first version focused on generated apps that can run locally without external services.
Suggested checks
Run mise run check-each init. Then run focused mise test:init cases for at least one Deno template and one Node.js or Bun template.
Why
fedify initcreates runnable apps, but generated projects do not have a standard local smoke-test command. A small generated task that starts the app and verifies a local actor lookup would help new users and would give contributors a clearer way to validate scaffold changes.Scope
Add a smoke-test task to generated projects from
@fedify/init. The task should be practical across supported package managers and should check the generated actor endpoint withfedify lookupor an equivalent local request.This will likely touch task generation in packages/init/src/action/, framework descriptions in packages/init/src/webframeworks/, and tests under packages/init/src/test/. Keep the first version focused on generated apps that can run locally without external services.
Suggested checks
Run
mise run check-each init. Then run focusedmise test:initcases for at least one Deno template and one Node.js or Bun template.