Remove dependency on @bigtest/performance

[cherewaty]

Motivation

thefrontside/bigtest#1006 (comment)

Approach

Remove the polyfill, since interactors are browser-only anyway.

After merge

Update sample app dependencies. The dev process for that part of this repo doesn't feel great, since with its own lock files it doesn't fit in the monorepo workflows.

[changeset-bot]

🦋 Changeset detected

Latest commit: 340ddad

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@interactors/html	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[netlify]

✔️ Deploy Preview for interactors canceled.

🔨 Explore the source changes: 340ddad

🔍 Inspect the deploy log: https://app.netlify.com/sites/interactors/deploys/613f566930f9350007ff1d67

[cherewaty]

@cowboyd you sure we can just switch to window.performance? Am I missing something obvious here re: environments?

[cowboyd]

@cherewaty Yup, it's just ponyfills for each environment: https://github.com/thefrontside/bigtest/blob/v0/packages/performance/package.json#L6

You can see the browser ponyfill just pulls them off globalThis https://github.com/thefrontside/bigtest/blob/v0/packages/performance/browser-ponyfill.js

You may want to use globalThis instead of window as that seems to be the preferred nomenclature these days.

GitHub

bigtest/package.json at v0 · thefrontside/bigtest

Ensure your React/Vue/Ember/anything app works perfectly across browsers. - bigtest/package.json at v0 · thefrontside/bigtest

GitHub

bigtest/browser-ponyfill.js at v0 · thefrontside/bigtest

Ensure your React/Vue/Ember/anything app works perfectly across browsers. - bigtest/browser-ponyfill.js at v0 · thefrontside/bigtest

[cherewaty]

Replaced by #73