Romaji to Kana Converter: Astro — Chapter 1, Exercise 1 ===================================================================== TASK Scaffold the project exactly as this chapter describes, confirm npm run dev serves the placeholder page at Astro's own default port, and inspect the real generated astro.config.mjs -- confirm the default output mode and that no adapter appears anywhere in it yet. SOLUTION Running through the chapter's own commands: npm create astro@latest -- romaji-converter-astro cd romaji-converter-astro npm run dev The dev server starts and prints a local URL -- Astro's own real default is http://localhost:4321. Opening that address in a browser shows Astro's own starter page (or, once the chapter's own placeholder index.astro has been pasted in, the "Romaji to Kana Converter / Setup confirmed" page described in the chapter itself). Either result confirms the same thing: a real, working Astro project, running with nothing beyond a default scaffold. Opening the real, generated astro.config.mjs shows something close to: import { defineConfig } from 'astro/config'; export default defineConfig({}); Two things are worth confirming by actually reading this file rather than assuming them: 1. There is no `output` key set anywhere in the config object. Astro doesn't need one written out explicitly for the default to apply -- leaving it unset IS choosing 'static', not an unfinished setup. 2. There is no `adapter` key either, and no adapter package (like @astrojs/node) appears in package.json's own dependencies. A default scaffold never installs one, since a purely static site has no server to run at all -- there's nothing for an adapter to attach to yet. WHY THIS WORKS AS AN ANSWER ---------------------------- It doesn't just claim the default output mode is 'static' -- it verifies that claim against the real, generated config file, and confirms the absence of an adapter the same way, rather than treating either fact as something to take on faith from the chapter text alone.