<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Project-References on PlumePHP</title><link>https://plumephp.com/tags/project-references/</link><description>Recent content in Project-References on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Sat, 26 Sep 2026 11:00:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/project-references/index.xml" rel="self" type="application/rss+xml"/><item><title>大型 TypeScript 项目架构：tsconfig 分层策略、monorepo paths 与 Project References</title><link>https://plumephp.com/typescript-project-architecture-tsconfig/</link><pubDate>Sat, 26 Sep 2026 11:00:00 +0800</pubDate><guid>https://plumephp.com/typescript-project-architecture-tsconfig/</guid><description>&lt;p&gt;&lt;strong&gt;当项目从&amp;quot;一个 src 目录&amp;quot;膨胀到&amp;quot;多包、多应用、多构建目标&amp;quot;时，tsconfig 的配置方式决定了团队的迭代效率与类型安全底线&lt;/strong&gt;。单文件 &lt;code&gt;tsconfig.json&lt;/code&gt; 在大型项目里是灾难的来源：前端构建目标、Node 脚本、测试环境共用一份配置，常常为了兼容最弱的环节而放松全局的类型检查。&lt;/p&gt;</description></item></channel></rss>