Open fmontes opened 11 months ago
The question becomes whether we need puppeteer at all. If I remove our explicit declaration in our package.json the main integrated build currently works on mac. Even if another package has a test dependency on it I would think that would only impact when that is actually used and in those cases we would still need to follow the steps for installing chromium, but just be removing the explicit dependency we prevent the need for every m1+ mac from needing to follow manual steps before building dotcms.
For what I can tell we're only using puppeteer for dotcms-webcomponents
e2e tests... but we are not running those, I see some options here:
User Story
As a dotCMS user, I want to be able to update puppeteer to 14.2.0 or above, so I can use the latest version of the library.
Acceptance Criteria
Proposed Objective
Core Features
Proposed Priority
Priority 3 - Average
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.:
N/A
Assumptions & Initiation Needs
Quality Assurance Notes & Workarounds
N/A
Sub-Tasks & Estimates: