Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: separate puppeteer and puppeteer-core #9023

Merged
merged 1 commit into from Oct 5, 2022
Merged

feat: separate puppeteer and puppeteer-core #9023

merged 1 commit into from Oct 5, 2022

Conversation

jrandolf
Copy link
Contributor

@jrandolf jrandolf commented Sep 28, 2022

This PR moves the puppeteer source code into separate monorepo packages:

  • puppeteer and puppeteer-core are now separated into their own packages.
  • puppeteer-core has a new exports called puppeteer-core/internal for internal usage.

Tests and various tools have been updated to accommodate the migration.

@jrandolf jrandolf force-pushed the monorepo-2 branch 9 times, most recently from 3b82d31 to 759f4da Compare September 28, 2022 21:01
@jrandolf jrandolf changed the base branch from main to monorepo September 28, 2022 21:01
@jrandolf jrandolf removed the request for review from mathiasbynens September 28, 2022 21:17
@jrandolf jrandolf force-pushed the monorepo-2 branch 11 times, most recently from 546b9a8 to 4d35735 Compare September 29, 2022 05:23
@mathiasbynens
Copy link
Member

I suspect Alex might have opinions on this. I’ll RLGTM this for now but please do address his feedback, if any, after landing!

@jrandolf jrandolf force-pushed the monorepo-2 branch 3 times, most recently from 3ddb0b4 to 95d7412 Compare September 29, 2022 08:08
Base automatically changed from monorepo to main September 29, 2022 08:08
@jrandolf jrandolf force-pushed the monorepo-2 branch 18 times, most recently from 42d3761 to 58f22cc Compare October 5, 2022 11:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants