• Replace read-pkg dependency with native Node.js fs/promises API
• Add inline readPkg() helper using readFile() and JSON.parse()
• Remove read-pkg from package.json dependencies
• Simplify package.json call from object to string parameter

Replace read-pkg with native fs implementation

• Replace read-pkg import with readFile from node:fs/promises
• Add new readPkg(cwd) async helper function that reads and parses package.json
• Update main() function call from readPkg({ cwd }) to readPkg(cwd)
• Maintain same functionality with native Node.js APIs

@packages/utils/pkg-check.js

Remove read-pkg dependency

• Remove read-pkg from dependencies list
• Reduce external dependency count by one

@packages/utils/package.json

Description

readPkg() calls JSON.parse() directly, so parse failures don’t include which package.json path was
being read. The top-level promise .catch rethrows the error without adding context, making
diagnostics harder.

Code

@packages/utils/pkg-check.js[R213-216]

+async function readPkg(cwd) {
+	const data = await readFile(path.join(cwd, "package.json"), "utf8");
+	return JSON.parse(data);
+}

Evidence

The new helper parses package.json via JSON.parse without wrapping errors or annotating them with
the file path; any resulting SyntaxError is propagated up to the top-level .catch which rethrows
as-is.

@packages/utils/pkg-check.js[213-216]
@packages/utils/pkg-check.js[124-141]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`readPkg(cwd)` reads and parses `package.json` with `JSON.parse(data)` directly. If parsing fails, the thrown error message typically won’t identify which file path was being parsed, and the top-level `.catch()` rethrows without adding that context.

### Issue Context
This script is a CLI utility (`pkg-check.js`). When it fails due to malformed JSON, the error should clearly identify the exact `package.json` file path to speed up debugging.

### Fix Focus Areas
- @packages/utils/pkg-check.js[213-216]
- @packages/utils/pkg-check.js[124-141]

### Suggested change
Wrap the parse in a `try/catch` and rethrow an error that includes the resolved `package.json` path (optionally using the `cause` option).

Example:
```js
async function readPkg(cwd) {
 const file = path.join(cwd, "package.json");
 const data = await readFile(file, "utf8");
 try {
   return JSON.parse(data);
 } catch (err) {
   // preserve stack/cause but add file context
   throw new Error(`Failed to parse ${file}: ${err.message}`, { cause: err });
 }
}
```

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools