Exercise 3: No Built-In ORM or Auth — Possible Solution
====================================================================

INSPECTING package.json
------------------------------
A freshly scaffolded Next.js project's package.json dependencies list
only next, react, and react-dom (plus TypeScript/ESLint-related
devDependencies if those options were accepted during setup). There is
no ORM package (no Prisma, no Drizzle, nothing database-related at all)
and no authentication package (no NextAuth/Auth.js, no session library)
present anywhere in the file.

WHAT A FRESH DJANGO OR RAILS PROJECT WOULD ALREADY INCLUDE
------------------------------
Per this chapter's own "Six Frameworks, Compared Honestly" table, Django
and Rails are both "batteries included": a fresh Django project's
INSTALLED_APPS already lists django.contrib.auth (a real, working
authentication app) and ships its own ORM as a core part of the
framework itself, not a separate install. A fresh Rails project
similarly ships ActiveRecord (its own built-in ORM) and
has_secure_password as a built-in authentication building block. Neither
framework needs a developer to choose or install a database or auth
library before starting real work - the choice is already made for
them.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly confirms the absence of any ORM/auth package in the actual
package.json rather than assuming it based on the chapter's own
description, and correctly names Django's django.contrib.auth/ORM and
Rails' ActiveRecord/has_secure_password as the concrete, real things a
Next.js project's own bare dependency list has no equivalent of yet -
directly explaining why Chapter 2 (Prisma) and Chapter 9 (authentication)
both have real decisions still ahead of them that Django/Rails would
never need to make in the same way.