---
title: "Comment by seth on \"Node.js TypeScript monorepo via NPM workspaces\" | Hashnode"
description: "Nice summary. A question about the placement of the rootDir and ourDir compiler options. Why not place that in the tsconfig.base.json? Then it only has to be do"
url: "https://hashnode.com/posts/nodejs-typescript-monorepo-via-npm-workspaces/62f8e35b69fa1793160c55e8/comment/63e28983cecce1c954ae00e8"
---

[Discussion](https://hashnode.com/posts/nodejs-typescript-monorepo-via-npm-workspaces/62f8e35b69fa1793160c55e8)

Comment [Node.js TypeScript monorepo via NPM workspaces](https://hashnode.com/posts/nodejs-typescript-monorepo-via-npm-workspaces/62f8e35b69fa1793160c55e8)

[seth](https://hashnode.com/@seth4520)

[Feb 7, 2023](https://hashnode.com/posts/nodejs-typescript-monorepo-via-npm-workspaces/62f8e35b69fa1793160c55e8/comment/63e28983cecce1c954ae00e8)

Nice summary. A question about the placement of the rootDir and ourDir compiler options. Why not place that in the tsconfig.base.json? Then it only has to be done once? Is there something about placing it there that changes things?

[Dávid Szabó](https://hashnode.com/@davidszabo)

[Feb 18, 2023](https://hashnode.com/posts/nodejs-typescript-monorepo-via-npm-workspaces/62f8e35b69fa1793160c55e8/comment/63e28983cecce1c954ae00e8#reply-63f0ab6a34c25f8061772f7b)

That would break the compilation because the paths are always relative to the original configuration file. In this case, specifying these paths in the tsconfig.base.json, would mean that the paths are relative to the base file.

[typescriptlang.org/tsconfig](https://www.typescriptlang.org/tsconfig#extends) Properties with relative paths found in the configuration file, which aren’t excluded from inheritance, will be resolved relative to the configuration file they originated in.
