Skip to content

environment.md

Latest commit

 

History

History
34 lines (25 loc) · 1.32 KB

environment.md

File metadata and controls

34 lines (25 loc) · 1.32 KB
Raw

Environment & dependencies

Node version

This project requires Node >=24.3.0 (the pinned remix@3.0.0-beta.10 engine).

In the Cursor Cloud VM, Node 24 is installed via nvm and made the default. The VM also ships a system Node 22 at /exec-daemon/node that would otherwise win on PATH, so ~/.bashrc prepends the nvm Node 24 bin to PATH. New shells get Node 24 automatically; if you spawn a non-login shell and see Node 22, select the nvm-managed Node 24 (no hard-coded patch version):

nvm use 24
# or, if nvm isn't loaded in this shell:
export PATH="$(dirname "$(nvm which 24)"):$PATH"

Install caveats

Install dependencies with npm install (npm is the package manager — there is a package-lock.json).

npm 11 (bundled with Node 24) prints allow-scripts warnings for blocked postinstall scripts (esbuild, @sentry/cli). This is safe to ignore:

  • esbuild works via its @esbuild/linux-x64 optional dependency.
  • @sentry/cli is only needed for source-map upload at build time, which is skipped unless SENTRY_AUTH_TOKEN is set. Production builds always emit public *.map files in dist/ (open source); when the token is present, those same maps are also uploaded to Sentry and left in the deploy.

npm run build, npm run dev, and the test suites all work without approving those scripts.