Which combination best describes how you read and extend package.json during generation?

• A. readJSON and extendJSON
• B. writeJSON and mergeJSON
• C. openJSON and updateJSON
• D. fetchJSON and modifyJSON

Answer: (A)

In Yeoman you manage existing JSON files, like package.json, using a two-step approach: read the current content and then extend it with new data. readJSON pulls the existing package.json so you can inspect its current fields, dependencies, scripts, and other settings. extendJSON then merges your new data into that existing object and writes it back, ensuring you add or update things without discarding what was already there. This pattern is ideal for adding dependencies, scripts, or metadata in a safe, idempotent way because it preserves the existing configuration while applying your changes. The other options describe methods or actions that aren’t the standard Yeoman file-system helpers for reading and merging JSON, so they wouldn’t properly read and extend package.json.