Fixed Nx cache outputs for parse-email-address package

[EvanHahn]

no ref

The build target compiled to build/ but Nx's default cache outputs only tracked dist, es, types, and umd, causing the directory to be missing after cache hits.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: aa166a77-1346-4041-815a-56218d496738

📥 Commits

Reviewing files that changed from the base of the PR and between c310fc7 and 4810eb0.

📒 Files selected for processing (1)

• ghost/parse-email-address/package.json

---

Walkthrough

An Nx configuration block has been added to the package.json file for the parse-email-address package. This configuration specifies the build target with its output directory set to build (relative to the project root). The addition comprises 7 new lines with no modifications to existing code or exported APIs.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: fixing Nx cache outputs for the parse-email-address package to include the build directory.
Description check	✅ Passed	The description clearly explains the problem and solution: the build target outputs to build/ but Nx's cache only tracked other directories, and this PR fixes that by updating cache outputs.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch parse-email-address-nx-fix

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[9larsons]

question (non-blocking): /build is an outlier here and /dist is the nx default, should we just be using that?