building the freeCodeCamp of codespaces don't work

[majestic-owl448]

It is not possible to build the site on codespaces, ports 3000 and 8000 never get populated

[TorresjDev]

I think it could be a typo from outdated docs for updates. When you open the repo in GitHub Codespaces, it should auto-build, and the port should be under 4321, though it may vary depending on your OS and or internet browser.

[majestic-owl448]

@TorresjDev have you tried? do the API and client build for you?

[TorresjDev]

Yes it builds and runs on port 4321, try running pnpm run develop on terminal

I used this markdown file to follow along
https://github.com/freeCodeCamp/contribute/blob/main/src/content/docs/how-to-setup-freecodecamp-locally.mdx

You can still run it under the GitHub Codespace they can the how-to guide section for it under the same url file

[majestic-owl448]

Still nothing, no port is engaged once it finishes doing things

also port 4321 is not part of the build process

oh, that's the port for the contribute repo, I mean the freeCodeCamp/freeCodeCamp repo

[TorresjDev]

Hey sorry, for the delay, but I have not been able to get it to build on my side either 🤷‍♂️ there seems to be errors when building but could be from missing variables from the .env file.

The package.json file also runs both servers for frontend and backend but I had issues with the gaspy when running develop

[gikf]

Following changes made it work for me:

• Selecting the 4-core for the machine type. With 2-core Building development bundle and Caching HTML renderer compilation were literally not finishing when starting developing client.
• Changing HOME_LOCATION and API_LOCATION in the .env file to addresses provided by codespaces, directing to the appropriate port (htts://something-8000.app.github.dev and htts://something-3000.app.github.dev). These can be copied in the Ports tab.
• Changing visibility of the port for API to Public. This step is required to not get CORS errors in client, when trying to contact API.

[Lauro235]

So I followed your instructions gikf.

• Update to 4-core instance ✅
• Create ./root/.env ✅
• Update env vars HOME_LOCATION and API_LOCATION to the open ports created and listed by codespaces ✅
• Changed API visibility to Public ✅

Running FCC_BLOCK=css-grid pnpm run clean-and-develop &> logs.txt

I get:

not finished Building development bundle - 30.976s

not finished Caching HTML renderer compilation - 1.878s

/workspaces/freeCodeCamp/node_modules/.pnpm/yoga-layout-prebuilt@1.10.0/node_modules/yoga-layout-prebuilt/yoga-layout/build/Release/nbind.js:53
        throw ex;
        ^

Error: Channel closed
    at process.target.send (node:internal/child_process:753:16)
    at onResult (/workspaces/freeCodeCamp/node_modules/.pnpm/gatsby-worker@0.6.0/node_modules/gatsby-worker/dist/child.js:38:5)
Emitted 'error' event on process instance at:
    at processEmit (/workspaces/freeCodeCamp/node_modules/.pnpm/signal-exit@3.0.7/node_modules/signal-exit/index.js:199:34)
    at process.emit (/workspaces/freeCodeCamp/node_modules/.pnpm/@turist+fetch@7.2.0_node-fetch@2.7.0/node_modules/@turist/fetch/dist/sourcemap-register.js:1:7334)
    at node:internal/child_process:757:35
    at processTicksAndRejections (node:internal/process/task_queues:85:11) {
  code: 'ERR_IPC_CHANNEL_CLOSED'
}

Node.js v22.21.1

Opening the client I get an HTTP 502 error. Not sure where I'm going wrong.

Edit: just to add that I've tried other commands like FCC_BLOCK='lab-boolean-check' pnpm run build:curriculum:content with repo suggested node version 22.21.1

[majestic-owl448]

@Lauro235 have you tried with Node 24?

[Lauro235]

@majestic-owl448

Hi there, so I'm thinking of re-editing my initial question, to simply stating some things that helped me, because along the way I got confused.

1. When prepending script with FCC_BLOCK= ensure block starts with either review-, workshop-, lab- or lecture-. My original build used FCC_BLOCK=css-grid which did not follow this new convention even though the block technically existed.
2. FCC_BLOCK='lab-boolean-check' pnpm run build:curriculum:content doesn't exist, I made a mistake, scrolling through old cli commands and posted the wrong command above. It should have been FCC_BLOCK='lab-boolean-check' pnpm run clean-and-develop. This does work after following the steps provided above from gikf
3. If using codespaces as is, playwright will not work and so running FCC_BLOCK=lab-boolean-check pnpm run test:curriculum:content will not run successfully. This is because you will be unable to download proper dependencies, because the capped playwright version v1.47.1 will not recognise Ubuntu 24. I believe that simply updating this to 1.57.0 will fix it, but am looking for other codespaces users to check this.

On the node question, I don't know how to override the version provided in the docker-compose.yml file on line 6 image: mcr.microsoft.com/devcontainers/typescript-node:22. Short of reinstalling a node version manager each time I log in which is a massive faff. I suggest someone who knows about devops, can provide fnm or nvm as an environment dep.

[majestic-owl448]

yeah, build:curriculum:content is not a valid command, to build use develop or clean-and-develop

[laxmanStarx]

Hello everyone! I m new to open source contribution, can you please assign me new easy tasks where i can understand and contribute to open source.

[majestic-owl448]

@laxmanStarx we do not assign issues, the issues with labels 'help wanted' or 'first timers only' are open for contributors to work on