build: Upgrade puppeteer and related dependencies

[tylerbutler]

wip

[jason-ha]

Lingering internal reference?

---

Refers to: pnpm-lock.yaml:22953 in 53eb47e. [](commit_id = 53eb47e, deletion_comment = False)

[tylerbutler]

  '@fluidframework/datastore-definitions': 2.0.0-internal.8.0.0

Okay with these changes?

Refers to: pnpm-lock.yaml:15730 in 53eb47e. [](commit_id = 53eb47e, deletion_comment = False)

Tough to see what you're referring to in the GitHub UI, but I do expect some internal8.0.0 entries in the lockfile since that's what the typetest "previous version" is right now.

[tylerbutler]

  '@fluidframework/datastore-definitions': 2.0.0-internal.8.0.0

Installed codeflow so I could see what you were referring to. I don't know how to keep pnpm from doing this. I can manually change them back to 8.0.0, but I don't know why pnpm changed themn in the first place.

---

In reply to: 1930739069

---

Refers to: pnpm-lock.yaml:15730 in 53eb47e. [](commit_id = 53eb47e, deletion_comment = False)

[tylerbutler]

Do you mean running pnpm dedupe or something else? pnpm dedupe produces a lot of churn.

---

In reply to: 1930753177

---

Refers to: pnpm-lock.yaml:28902 in 53eb47e. [](commit_id = 53eb47e, deletion_comment = False)

[jason-ha]

  '@fluidframework/datastore-definitions': 2.0.0-internal.8.0.0

Installed codeflow so I could see what you were referring to. I don't know how to keep pnpm from doing this. I can manually change them back to 8.0.0, but I don't know why pnpm changed themn in the first place.

In reply to: 1930739069

Refers to: pnpm-lock.yaml:15730 in 53eb47e. [](commit_id = 53eb47e, deletion_comment = False)

Sorry, I thought the UI would be okay so long as I stuck to whole lines. I guess it can only be a single line.
I wanted to reference multiple lines in places.
The is a lot of duplication and maybe also inconsistent references to some packages like there are three versions of @fluidframework/core-interfaces.

[tylerbutler]

Regarding the lockfile changes, I reset the lockfile to main, nuked node-modules, and ran pnpm i again. Is there something else I should do to minimize lockfile churn?

[jason-ha]

Do you mean running pnpm dedupe or something else? pnpm dedupe produces a lot of churn.

In reply to: 1930753177

Refers to: pnpm-lock.yaml:28902 in 53eb47e. [](commit_id = 53eb47e, deletion_comment = False)

If there was going to be a full dedupe, my experience is that it should be done apart from any other change. You just can't figure out what is going on with dedupe and other changes at the same time unless dedupe is done with every dep change.
So I meant less aggressive which is perhaps manual.

[jason-ha]

Regarding the lockfile changes, I reset the lockfile to main, nuked node-modules, and ran pnpm i again. Is there something else I should do to minimize lockfile churn?

You shouldn't need to nuke node_modules. But if you do, then you should use pnpm i --frozen-lockfile. If you ran without frozen and got no changes cool. If you got changes that you like, then perhaps we submit those; so we can tease things apart. I just wouldn't expect and fluidframework references to change in this PR.

[jason-ha]

I see two things. Remove examples/utils/bundle-size-tests @types/puppeteer reference and if possible the "puppeteer" in tsconfig "types" lines.