Closed websi closed 1 year ago
chromium is installed globally via package system, you should not need to install another chromium. I don't know playwright though - maybe it just needs a variable or something to get the path? See the pupeteteer one in the image. Sounds a little bit like https://github.com/garris/BackstopJS/issues/1454
Why do you think it is not available for the node user, backstopjs running as user node does find it ... Must be some playwright exclusive problem here.
@websi Can you add a small reproducer (branch) somewhere which does show your issue to analyze / help further?
Running into the same issue.
@tkrah I made a small repo where this can be reproduced.
Running into the same issue.
@tkrah I made a small repo where this can be reproduced.
COMMAND | TypeError: Cannot read properties of undefined (reading 'replace')
at Object.makeSafe (/usr/local/lib/node_modules/backstopjs/core/util/engineTools.js:48:14)
at module.exports.runPlaywright (/usr/local/lib/node_modules/backstopjs/core/util/runPlaywright.js:51:41)
at /usr/local/lib/node_modules/backstopjs/node_modules/p-map/index.js:57:28
trying to run your backstop example just always ends in that for me, ideas? using npm 9.6.2 with node 18.x.
trying to run your backstop example just always ends in that for me, ideas? using npm 9.6.2 with node 18.x.
@tkrah Sorry forgot to make .nvmrc
. I'm on node - 16.14.2
npm - 8.19.4
trying to run your backstop example just always ends in that for me, ideas? using npm 9.6.2 with node 18.x.
@tkrah Sorry forgot to make
.nvmrc
. I'm onnode - 16.14.2
npm - 8.19.4
fix is already merged, does it help you?
@websi @tsvetislavt99 Do you still have that problem with 6.2.2? Should be working again now.
@tkrah Hey, yes I can confirm the issue is resolved with me.
I can also confirm that the issue was resolved.
With Version 6.2.0 the chromium browser is not available for non root user. The normal user is
node
. See https://github.com/garris/BackstopJS/blob/1144782deebfe7e70650f09cc7fa2d3ffb349f7a/docker/Dockerfile#L18Current workaround is to start the image as root user.