[LanieOkorodudu]

Description of what you did:
This follows on from #1872
I've updated the tests to use dynamic import() so they work with Puppeteer 25. I also updated the Jest test command to run --experimental-vm-modules to support ESM. I tested the changes with Puppeteer 25.13.0 locally and the test and build are all passing.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
universalviewer	Ready	Preview	Oct 20, 2026 2:53pm UTC

[vercel]

@LanieOkorodudu is attempting to deploy a commit to the Universal Viewer Team on Vercel.

A member of the Team first needs to authorize it.

[demiankatz]

Thanks, @LanieOkorodudu; I don't love being dependent on an experimental feature, but since this is only used for running tests, and if tests fail, we will immediately know about it, I suppose I can live with it if other approaches are unavailable or prohibitively complicated.

Since I just merged several new tests (in #1796), do you mind merging the dev branch into this PR so we can double-check that everything still passes? If so, I can approve and merge as long as nobody else objects in the meantime.

[demiankatz]

@LanieOkorodudu, it might also be a good idea to merge in the latest jest release from #1872, since Dependabot has come up with a new version since we started this work.

[demiankatz]

(Never mind, I see you're already ahead of me and have done that!) :-)

[LanieOkorodudu]

Thanks, @LanieOkorodudu; I don't love being dependent on an experimental feature, but since this is only used for running tests, and if tests fail, we will immediately know about it, I suppose I can live with it if other approaches are unavailable or prohibitively complicated.

Since I just merged several new tests (in #1796), do you mind merging the dev branch into this PR so we can double-check that everything still passes? If so, I can approve and merge as long as nobody else objects in the meantime.

@demiankatz, Thanks for the feedback. Now dependabot just update it again 25.14.0. I will try my best to fix and finish it today.

[LanieOkorodudu]

@demiankatz, I have updated the branch with the latest changes from upstream/dev and the Puppeteer 25.14.0 update from #1889 .
And yes I agree with your point that relying on a experimental Node.js feature is not ideal. I think it's reasonable approach for now. Otherwise, we could look at migrating our Jest setup from CommonJS to ESM as a separate piece of work.

[demiankatz]

Thanks, @LanieOkorodudu, this looks reasonable to me. I think we have two options:

1.) I can approve and merge, and we can open an issue to track the need to migrate the Jest setup in future so we can eliminate the experimental feature.

2.) We can leave this open and put it in the appropriate section of the community board for discussion at the next Community Call in case others have concerns or are willing to help with the larger configuration improvement.

Please let me know if you have thoughts/preferences and I'll take the appropriate action!

[LanieOkorodudu]

Thanks, @LanieOkorodudu, this looks reasonable to me. I think we have two options:

1.) I can approve and merge, and we can open an issue to track the need to migrate the Jest setup in future so we can eliminate the experimental feature.

2.) We can leave this open and put it in the appropriate section of the community board for discussion at the next Community Call in case others have concerns or are willing to help with the larger configuration improvement.

Please let me know if you have thoughts/preferences and I'll take the appropriate action!

Thanks @demiankatz, We can merge this for now to address the #1889, and I will open an issue to track the need to migrate the Jest setup which I can start working on it from my side.

[demiankatz]

Thanks, @LanieOkorodudu -- in that case, I'll approve and merge this to get things resolved.

[demiankatz]

Oh, drat, the recent Dependabot PRs have introduced a conflict here in package-lock.json, and I don't currently have an environment set up where I can quickly fix it. Can you just delete package-lock.json, run npm i, and commit the result to get this back up to date? (I'll do it later if you don't have time either... but right now I need to get ready for the sprint!)

[LanieOkorodudu]

Oh, drat, the recent Dependabot PRs have introduced a conflict here in package-lock.json, and I don't currently have an environment set up where I can quickly fix it. Can you just delete package-lock.json, run npm i, and commit the result to get this back up to date? (I'll do it later if you don't have time either... but right now I need to get ready for the sprint!)

Thanks @demiankatz, All done now.

[demiankatz]

Thanks again, @LanieOkorodudu!