Chrome path is not being set correctly on mac when deploying VlocityCard

[vernemi2]

When running the following command:
vlocity -sfdx.username <<my-sf-org-username>> -job VlocityJob.yaml packDeploy

The VlocityJob.yaml:

projectPath: .
expansionPath: vlocity
autoRetryErrors: true
activate: true
useSfdxCli: true
ignoreLocalCompilationCards: true
manifest:
  - VlocityCard/cpqQuoteButtonsMobile

I'm getting following error:
Puppeteer initialization Failed, LWC Activation disabled - Error: Failed to launch the browser process! spawn /usr/bin/chromium-browser ENOENT

When I try to override the path in the VlocityJob.yaml file with:
puppeteerExecutablePath: /Applications/Google Chrome.app
I'm getting the same error.

When looking through the repo it looks like I'm hitting this condition (https://github.com/vlocityinc/vlocity_build/blob/master/lib/utilityservice.js#L1657):

} else if (fs.existsSync(linux3)) {
        puppeteerOptions.executablePath = linux3;        
    }

While the puppeteerExecutablePath is being completely ignored for some reason.

My config:

• Apple M2 Pro, Sonoma 14.2
• Vlocity Build v1.17.6
• Puppeteer 21.7.0

[pawel-id]

The issue is because ancient dependencies of VBT. It fails on Apple silicon. In this particular example it is about puppeteer-core@5. See old (and actually not solved) issue #519

local workaround:

1. clone repo locally: git clone [email protected]:vlocityinc/vlocity_build.git
2. cd into this cd vlocity_build
3. install dependencies npm i
4. bump puppeteer a bit npm i puppeteer-core@6
5. link this version to be used locally npm link
6. from this moment you local vlocity command will point to your local clone with workaround

[vernemi2]

Hi @pawel-id,

That did the trick.

Thanks a lot for your help.
Michal

[Schuchie]

FYI: SF-Support: The issue will be solved in version 254 (coming in December).