chore(repo): improve the devcontainer setup

[tinesoft]

• respect pnpm version declared in root package.json
• improve performances when installing node modules
• add troubleshooting instructions in CONTRIBUTING.md to help solve common issue related to outdated GLIBC version

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Aug 10, 2024 5:21am

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 3dd72fb. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 4 targets

• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=a13961d8fcf3457ce6e0fbf9871a524e9466072a --head=3dd72fbf1e8c2cc1f084255a4d190de5de51c40e
• nx affected --targets=lint,test,build,e2e,e2e-ci --base=a13961d8fcf3457ce6e0fbf9871a524e9466072a --head=3dd72fbf1e8c2cc1f084255a4d190de5de51c40e --parallel=3
• nx documentation --no-dte

---

Sent with 💌 from NxCloud.

[isaacplmann]

I'll let Jason or Victor approve the changes. The docs look fine.

How often does the version of glibc get updated? Is there a way to automatically use the latest version?

[tinesoft]

From what I have understood, GLIBC is used to compile native stuff used by Nx ( i.e rust related code), so I would say that the version of the compiler library need to evolve along with the version of rust Rust language and features that are used in the project.

When I initially setup the devcontainer, v2.31 of GLIBC was needed, now it is v2.33 at minimum

[tinesoft]

also I think the sudo apt-get update performed whenever the devcontainer is created (see postCreateCommand.sh) will take care of automatically updating the glibc binaries, but that would only be for minor/fix versions (this has already worked before when I first created the devcontainer setup)

As for automating the entire thing starting from the base image that is used by the devcontainer, maybe we can create a small script that would extract it and run the underlying docker command to build/mount the container and then nx build command as part of an e2e nightly test...

That way we can spot when the image needs to be updated.

I can look into that and provide another PR if the idea is validated?

[tinesoft]

Any progress on reviewing this ? @FrozenPandaz @vsavkin

[tinesoft]

Thanks for approving/merging this.

Another thing that we can do, to optimize/improve the DX when opening the repo in Github Codespaces, is to activate the pre-built image of the underlying devcontainer, so that future contributors can get started more quickly (no need to wait for the initial build of image)

Then

[tinesoft]

Isaac: How often does the version of glibc get updated? Is there a way to automatically use the latest version?

@isaacplmann do you want me to investigate how to automate the update of the devcontainer image as described here ?

[isaacplmann]

I wouldn't worry about doing that right now. If it is automatically handling patch and minor versions, we can manually handle major versions.

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.