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

WHAT package.json ACTUALLY CONTAINS
------------------------------
Per this chapter, a freshly scaffolded Astro project's package.json lists only astro itself as a dependency (plus whatever UI framework integrations were selected during scaffolding, if any) - no database driver, no ORM package, and no authentication library appears anywhere in dependencies or devDependencies by default.

THE CONTRAST WITH RAILS AND LARAVEL
------------------------------
Per this chapter, a fresh Rails project's own Gemfile already includes ActiveRecord (bundled as part of the rails gem itself) and, once bcrypt is uncommented, a real password-hashing library ready to back has_secure_password. A fresh Laravel project's own composer.json already includes Eloquent and the framework's own Auth facade, both part of the core laravel/framework package. Astro's package.json has no equivalent of either - both the ORM and the auth layer are entirely absent until a developer deliberately chooses and installs them.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly describes what a fresh Astro project's package.json does and doesn't contain, and correctly contrasts that absence against Rails' and Laravel's own bundled ORM and auth dependencies, grounding the chapter's own "bring your own backend" claim in an actual, checkable file rather than an assertion.