NextJS: Build components to export and pull into a different project - next.js

Question

Current Setup: I have two NextJS apps: one we'll call Project A and a library repo that we'll call Project LIB. Project A is a fairly simple app that has a couple independent components whereas Project LIB is a library-like app that many other apps leverage.
What I am trying to do: Package up Project A in a way where the build distribution contains all of its components that I can then leverage in Project LIB. I am currently building/deploying Project A as a private repo and pulling it into Project LIB using npm install git#github.com:<organization>/<Project A>.git and that is working fine. My current issue is that only the pages are being build when I build Project A using npm run build and it doesn't also generate each component's corresponding .d.ts file under /components.
I figured setting "declaration": true /* Generates corresponding '.d.ts' file. */ would generate the components for me but that didn't seem to do the trick. I'm also not finding much online regarding how to do this. Maybe i'm just a bad googler, who knows.
Anyways, here's what my tsconfig and package.json files looks like:
package.json:
{
...,
"files": [
"lib/**/*"
]
}
tsconfig.json:
{
"compilerOptions": {
"target": "es5",
"module": "ESNext",
"lib": [
"dom",
"dom.iterable",
"esnext"
],
"allowJs": true,
"jsx": "preserve",
"declaration": true,
"declarationMap": true,
"sourceMap": true,
"outDir": "./lib",
"rootDir": "./",
"removeComments": true,
"noEmit": true,
"isolatedModules": true,
"strict": true,
"moduleResolution": "node",
"esModuleInterop": true,
"skipLibCheck": true,
"forceConsistentCasingInFileNames": true,
"resolveJsonModule": true
},
"include": [
"next-env.d.ts",
"**/*.ts",
"**/*.tsx",
"components/**/*"
],
"exclude": [
"node_modules/*",
"./node_modules",
"./node_modules/*",
"./lib"
]
}