Romaji to Kana Converter: Angular & Express — Chapter 1, Exercise 2
=====================================================================

TASK
Run ng new in a separate scratch folder with no flags at all, and
inspect the real generated file structure -- confirm there's no
routing module and no SSR-related files, and confirm the root
component's own real file names match this chapter's own finding-box.

SOLUTION

  cd /tmp
  ng new scratch-test
  # answer any interactive prompts with the defaults

  cd scratch-test
  ls src/app/

Observed real output (file names, not exhaustive):

  app.ts
  app.html
  app.css
  app.config.ts
  app.routes.ts   -- present only if routing was accepted at the prompt

Confirming no routing module exists (assuming routing was declined, or
the --routing flag was never passed): no app-routing.module.ts or
equivalent NgModule-based routing file appears anywhere in src/app/ --
routing in a modern Angular app is either a plain app.routes.ts array
consumed by provideRouter(), or entirely absent if never requested.

Confirming no SSR files exist: no server.ts, no server-related entries
in angular.json's own "architect" section, and no @angular/ssr
dependency in package.json -- all real, direct evidence that
server-side rendering was never scaffolded, since it was never
explicitly requested.

Confirming the root component's own real file names: opening
src/app/app.ts directly shows a real, working component definition --
no app.component.ts exists anywhere in the project at all, matching
the chapter's own finding-box claim about the current "2025" file
naming style.

WHY THIS WORKS AS AN ANSWER
----------------------------
It runs the real Angular CLI directly, in a genuinely fresh scratch
project, and inspects the actual generated files rather than trusting
the chapter's own description secondhand -- confirming both the
routing/SSR-off-by-default claim and the file-naming claim against
real, current CLI output.