Exercise 2: Create an extensions.json — Possible Solution
====================================================================

STEPS
------------------------------
1. In your open project's root, create a folder named exactly
   ".vscode" if one doesn't already exist (note the leading dot).
2. Inside it, create a file named "extensions.json" with the
   following content, reusing two of Chapter 4's essential picks:

{
  "recommendations": [
    "dbaeumer.vscode-eslint",
    "esbenp.prettier-vscode"
  ]
}

   (The strings here are each extension's unique ID, found on its
   Marketplace detail page under "More Info" — not just its display
   name.)

3. Save the file.
4. Close the folder entirely (File -> Close Folder), then reopen it
   (File -> Open Folder... and select the same folder again).
5. VS Code should show a notification in the bottom-right: "This
   workspace has extension recommendations" (or similar), with a
   button to review and install them.

WHY THIS WORKS AS AN ANSWER
------------------------------
Placing extensions.json inside .vscode/ (not the project root itself)
reuses the exact file location the chapter specifies — this is the
same folder .vscode/settings.json from Exercise 1 lives in, and VS
Code specifically watches this location for both files.

Using ESLint's and Prettier's real extension IDs reuses the chapter's
own worked example directly, rather than invented placeholder names —
the IDs must match real Marketplace extensions for the install prompt
to correctly identify and offer them.

Closing and reopening the folder is necessary because the
recommendation prompt is triggered specifically when a workspace is
OPENED, per the chapter's own description ("when someone opens this
folder for the first time") — simply saving the file while the folder
is already open won't retroactively trigger the same notification.