How to test v5 Candidate

[vishnuc]

Hi , Previously I would just run npm run build and it worked fine , now its giving lots of error

npm error code 1
npm error path /Users/vishnuc/Desktop/project/node_test/tv5/lightweight-charts/node_modules/@memlab/core/node_modules/puppeteer
npm error command failed
npm error command sh -c node install.mjs
npm error Error: ERROR: Failed to set up chrome-headless-shell v127.0.6533.88! Set "PUPPETEER_SKIP_DOWNLOAD" env variable to skip download.
npm error     at file:///Users/vishnuc/Desktop/project/node_test/tv5/lightweight-charts/node_modules/@memlab/core/node_modules/puppeteer/lib/esm/puppeteer/node/install.js:84:27
npm error     at async Promise.all (index 1)
npm error     at async downloadBrowser (file:///Users/vishnuc/Desktop/project/node_test/tv5/lightweight-charts/node_modules/@memlab/core/node_modules/puppeteer/lib/esm/puppeteer/node/install.js:90:9) {
npm error   [cause]: [Error: ENOENT: no such file or directory, open '/Users/vishnuc/Desktop/project/node_test/tv5/lightweight-charts/node_modules/.cache/puppeteer/chrome-headless-shell/127.0.6533.88-chrome-headless-shell-mac-arm64.zip'] {
npm error     errno: -2,
npm error     code: 'ENOENT',
npm error     syscall: 'open',
npm error     path: '/Users/vishnuc/Desktop/project/node_test/tv5/lightweight-charts/node_modules/.cache/puppeteer/chrome-headless-shell/127.0.6533.88-chrome-headless-shell-mac-arm64.zip'
npm error   }
npm error }
npm error A complete log of this run can be found in: /Users/vishnuc/.npm/_logs/2025-01-07T12_41_03_743Z-debug-0.log

[SlicedSilver]

If you aren't trying to run the screenshot (or other e2e tests) then you can use the following command when installing the npm packages:

PUPPETEER_SKIP_DOWNLOAD=true npm install

otherwise if you do want to run the e2e tests then you might need to nuke your node_modules folder (delete it) and clear out your npm cache before trying to run npm install again. However another option to try is to remove the cacheDirectory setting in the .puppeteerrc.cjs file before running npm install. This would most likely fix your issue.

We install the chrome binary within the node_modules/.cache/puppeteer folder so that it is correctly cached and reused across our CI pipeline actions, however this may not work correctly for you depending on the steps you are taking during the installation phase.

[vishnuc]

Thanks , if I want to use in my production site , I want to use build:prod or build:release