Exercise 1: Building the Project and Checking Versions — Possible Solution
============================================================================

Follow Steps 1-5 of the chapter. A successful run looks like:

  $ npx tsx script.ts
  Created: { id: 1, email: 'ada@example.com', name: 'Ada' }
  All users: [ { id: 1, email: 'ada@example.com', name: 'Ada' } ]

Check the installed versions:

  $ npx prisma --version        # shows prisma and @prisma/client versions
  $ npm ls prisma @prisma/client @prisma/adapter-better-sqlite3

Every Prisma package should report a 7.x version (7.10.0 at the time
of writing), and they should all match.

Why this matters right now:

The npm "latest" tag for the prisma package currently points to a
Prisma 8 release candidate. If any Prisma package was installed
without @7 — for example by copying an install command from another
guide — you can end up with Prisma 8, or with a mix of 7 and 8. Prisma
8 uses a different configuration format and setup, so this course's
instructions won't match, and mismatched versions can fail in
confusing ways. Checking the versions first saves a lot of
head-scratching later.

WHY THIS WORKS AS AN ANSWER
------------------------------
It confirms the project works, shows two ways to check versions, and
explains the real risk behind pinning. Exact version numbers will
change over time.