Custom theme sub-packages in the mono repo cannot use Node-related APIs.

[shellRaining]

https://stackblitz.com/~/github.com/shellRaining/shellRaining-blog
https://github.com/shellRaining/shellRaining-blog

I plan to create a VitePress theme, and organized my VitePress blog into a mono repo. The directory structure is as above

you can see in theme/src/config.ts, there exist a buildEnd hook, it is used for counting word in my blog, which use readFileSync. Since it is a TypeScript file, I used tsup to compile it

Next is my blog post subpackage, which installs the theme subpackage via the workspace (I hope users can directly install my subpackage and use my custom theme). Its .vitepress/config.ts content has a extends field, I hope this could extend custom theme config

when I run vitepress build in content subpackage, it occurs error as below

[plugin vite:resolve] Module "node:fs" has been externalized for browser compatibility, imported by "/Users/shellraining/Documents/blog/packages/theme/src/config.ts". See https://vite.dev/guide/troubleshooting.html#module-externalized-for-browser-compatibility for more details.
x Build failed in 2.19s
✖ building client + server bundles...
build error:
../theme/src/config.ts (7:9): "readFileSync" is not exported by "__vite-browser-external", imported by "../theme/src/config.ts".
file: /Users/shellraining/Documents/blog/packages/theme/src/config.ts:7:9

5: import markdownItSub from "markdown-it-sub";
6: import markdownItTaskLists from "markdown-it-task-lists";
7: import { readFileSync } from "node:fs";
            ^
8:
9: const APPEARANCE_KEY = "shellRaining-blog-theme";

    at getRollupError (file:///Users/shellraining/Documents/vitepress/node_modules/.pnpm/rollup@4.34.7/node_modules/rollup/dist/es/shared/parseAst.js:397:41)
    at error (file:///Users/shellraining/Documents/vitepress/node_modules/.pnpm/rollup@4.34.7/node_modules/rollup/dist/es/shared/parseAst.js:393:42)
    at Module.error (file:///Users/shellraining/Documents/vitepress/node_modules/.pnpm/rollup@4.34.7/node_modules/rollup/dist/es/shared/node-entry.js:16603:16)
    at Module.traceVariable (file:///Users/shellraining/Documents/vitepress/node_modules/.pnpm/rollup@4.34.7/node_modules/rollup/dist/es/shared/node-entry.js:17052:29)
    at ModuleScope.findVariable (file:///Users/shellraining/Documents/vitepress/node_modules/.pnpm/rollup@4.34.7/node_modules/rollup/dist/es/shared/node-entry.js:14709:39)
    at ChildScope.findVariable (file:///Users/shellraining/Documents/vitepress/node_modules/.pnpm/rollup@4.34.7/node_modules/rollup/dist/es/shared/node-entry.js:5582:38)
    at FunctionScope.findVariable (file:///Users/shellraining/Documents/vitepress/node_modules/.pnpm/rollup@4.34.7/node_modules/rollup/dist/es/shared/node-entry.js:5582:38)
    at FunctionBodyScope.findVariable (file:///Users/shellraining/Documents/vitepress/node_modules/.pnpm/rollup@4.34.7/node_modules/rollup/dist/es/shared/node-entry.js:5582:38)
    at BlockScope.findVariable (file:///Users/shellraining/Documents/vitepress/node_modules/.pnpm/rollup@4.34.7/node_modules/rollup/dist/es/shared/node-entry.js:5582:38)
    at BlockScope.findVariable (file:///Users/shellraining/Documents/vitepress/node_modules/.pnpm/rollup@4.34.7/node_modules/rollup/dist/es/shared/node-entry.js:5582:38)
error: script "build" exited with code 1

However, if the buildEnd hook function is moved to the config.ts under the content sub-package (i.e., the configuration introduced via extend does not include the buildEnd hook), it does not throw this error and works normally. May I ask how to fix this?

you can test in stackblitz, it's output is same as my computer

[brc-dd]

You'll need 2 entrypoints in your theme. One for client, one for node. Currently both server side and browser code is being compiled into single file by tsup.

Ah, I see you're already doing that. I think you need to remove export * from config here - https://github.com/shellRaining/shellRaining-blog/blob/main/packages/theme/src/index.ts

[shellRaining]

Thanks, I exported them all in one go when I was writing the code earlier, and then forgot to delete them later😂. No wonder there were issues with the client.