Cloudflare workers hitting fatal error when building observable framework

[jaanli]

Hi! I am using Observable Framework for my personal blog: https://github.com/jaanli/jaan.li

However, I run into this issue when using the Cloudflare deploy script:

2024-10-05T14:41:21.022074Z	Cloning repository...
2024-10-05T14:41:21.713737Z	From https://github.com/jaanli/jaan.li
2024-10-05T14:41:21.714236Z	 * branch            7110abe94b0113eb7b913fc213973f9d648fcdbb -> FETCH_HEAD
2024-10-05T14:41:21.714338Z	
2024-10-05T14:41:21.755433Z	HEAD is now at 7110abe update
2024-10-05T14:41:21.755815Z	
2024-10-05T14:41:21.837575Z	
2024-10-05T14:41:21.838026Z	Using v2 root directory strategy
2024-10-05T14:41:21.861936Z	Success: Finished cloning repository files
2024-10-05T14:41:28.326822Z	Failed: error occurred while running build command

Is there a best way to debug this error?

I ran yarn upgrade recently, which was the only change.

The deploy script is here: https://github.com/jaanli/jaan.li/blob/main/.github/workflows/deploy.yml which was taken from an example.

Relevant thread: #1378

[jaanli]

Here is the error I am getting:

2024-10-06T14:44:20.631134Z	Cloning repository...
2024-10-06T14:44:23.323574Z	From https://github.com/jaanli/jaan.li
2024-10-06T14:44:23.324108Z	 * branch            b763e104c3d98e80499bda1e4996b0ea085a59b9 -> FETCH_HEAD
2024-10-06T14:44:23.324216Z	
2024-10-06T14:44:23.704644Z	HEAD is now at b763e10 update
2024-10-06T14:44:23.705172Z	
2024-10-06T14:44:23.786255Z	
2024-10-06T14:44:23.787209Z	Using v2 root directory strategy
2024-10-06T14:44:23.812011Z	Success: Finished cloning repository files
2024-10-06T14:44:25.373685Z	Checking for configuration in a wrangler.toml configuration file (BETA)
2024-10-06T14:44:25.374707Z	
2024-10-06T14:44:25.511907Z	No wrangler.toml file found. Continuing.
2024-10-06T14:44:25.66256Z	Detected the following tools from environment: [email protected], [email protected]
2024-10-06T14:44:25.663325Z	Installing project dependencies: yarn
2024-10-06T14:44:26.235957Z	➤ YN0070: Migrating from Yarn 1; automatically enabling the compatibility node-modules linker 👍
2024-10-06T14:44:26.236352Z	
2024-10-06T14:44:26.282409Z	➤ YN0000: ┌ Resolution step
2024-10-06T14:44:27.405363Z	➤ YN0061: │ glob@npm:8.1.0 is deprecated: Glob versions prior to v9 are no longer supported
2024-10-06T14:44:27.484867Z	➤ YN0061: │ inflight@npm:1.0.6 is deprecated: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
2024-10-06T14:44:27.604556Z	➤ YN0032: │ fsevents@npm:2.3.3: Implicit dependencies on node-gyp are discouraged
2024-10-06T14:44:29.128778Z	➤ YN0002: │ @observablehq/framework@npm:1.12.0 doesn't provide @types/markdown-it (pd6a79), requested by markdown-it-anchor
2024-10-06T14:44:29.129034Z	➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
2024-10-06T14:44:29.132971Z	➤ YN0000: └ Completed in 2s 850ms
2024-10-06T14:44:29.156096Z	➤ YN0000: ┌ Post-resolution validation
2024-10-06T14:44:29.156311Z	➤ YN0028: │ The lockfile would have been modified by this install, which is explicitly forbidden.
2024-10-06T14:44:29.156447Z	➤ YN0000: └ Completed
2024-10-06T14:44:29.15655Z	➤ YN0000: Failed with errors in 2s 876ms
2024-10-06T14:44:29.183266Z	Error: Exit with error code: 1
2024-10-06T14:44:29.183447Z	    at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
2024-10-06T14:44:29.183569Z	    at Object.onceWrapper (node:events:652:26)
2024-10-06T14:44:29.183678Z	    at ChildProcess.emit (node:events:537:28)
2024-10-06T14:44:29.183779Z	    at ChildProcess._handle.onexit (node:internal/child_process:291:12)
2024-10-06T14:44:29.193078Z	Failed: build command exited with code: 1
2024-10-06T14:44:31.045024Z	Failed: error occurred while running build command

[jaanli]

Fixed:

• Removed the lock file and ran yarn install again
• cloned the repo from scratch
• switched to github pages due to the file size restrictions