Contributing / Working on Sveltia CMS locally

[m4rrc0]

Note: I know you are not officially accepting contributions right now so feel free to disregard this issue if the time is not right for you to look into this.

I tried cloning the Sveltia CMS repo locally but building fails with the following error:

error during build:
[generate-extra-files] No input files
    at createProgram (/home/marc/code/libraries/sveltia/sveltia-cms/node_modules/.pnpm/ts-json-schema-generator@2.4.0/node_modules/ts-json-schema-generator/dist/factory/program.js:59:15)
    at createGenerator (/home/marc/code/libraries/sveltia/sveltia-cms/node_modules/.pnpm/ts-json-schema-generator@2.4.0/node_modules/ts-json-schema-generator/dist/factory/generator.js:11:52)
    at generateSchema (file:///home/marc/code/libraries/sveltia/sveltia-cms/node_modules/.vite-temp/vite.config.js.timestamp-1753439472996-2a1e8134adf91.mjs:69:8)
    at Object.handler (file:///home/marc/code/libraries/sveltia/sveltia-cms/node_modules/.vite-temp/vite.config.js.timestamp-1753439472996-2a1e8134adf91.mjs:86:13)
    at async Promise.all (index 7)
    at async PluginDriver.hookParallel (file:///home/marc/code/libraries/sveltia/sveltia-cms/node_modules/.pnpm/rollup@4.45.1/node_modules/rollup/dist/es/shared/node-entry.js:22213:9)
    at async file:///home/marc/code/libraries/sveltia/sveltia-cms/node_modules/.pnpm/rollup@4.45.1/node_modules/rollup/dist/es/shared/node-entry.js:23182:13
    at async catchUnfinishedHookActions (file:///home/marc/code/libraries/sveltia/sveltia-cms/node_modules/.pnpm/rollup@4.45.1/node_modules/rollup/dist/es/shared/node-entry.js:22655:16)
    at async rollupInternal (file:///home/marc/code/libraries/sveltia/sveltia-cms/node_modules/.pnpm/rollup@4.45.1/node_modules/rollup/dist/es/shared/node-entry.js:23179:5)
    at async buildEnvironment (file:///home/marc/code/libraries/sveltia/sveltia-cms/node_modules/.pnpm/vite@7.0.5_@types+node@24.1.0_sass@1.89.2_yaml@2.8.0/node_modules/vite/dist/node/chunks/dep-Bg4HVnP5.js:34135:12)
 ELIFECYCLE  Command failed with exit code 1.

Any idea where this comes from?

[munxar]

Hey @m4rrc0

I had a similar problem first, but it works when I removed the pnpm-lock.yaml.
afaik this can happen, if the architectures of the machine writing the lock file differ from the ones that install (arm, amd64m,...)

that worked for me:

rm pnpm-lock.yaml
pnpm i
pnpm build

hope this helps

[kyoshino]

If I take a close look at pnpm-lock.yaml carefully, I see fsevents only has the macOS (Darwin) variant. I’m on a Mac. Not sure how to fix it, but it’s probably the root cause of the error.

[kyoshino]

Nope, it seems fsevents is only required on Mac. Something else is probably not compatible with Windows or Linux.

[m4rrc0]

Thanks @munxar ! It solves the issue indeed.
What an annoying problem... It defeats the whole purpose of having a lockfile... 😅

In case anyone wants to take a look, I pushed the diff with my lockfile in this commit. I didn't find much to look at except version bumps.

[kyoshino]

Not sure if it’s related, but some dependencies were not built when running pnpm i. I’ve updated package.json to handle this.