chore: disable typescript + eslint during next.js builds

[james-elicx]

The typescript and eslint checks slow down our e2e builds while providing zero value. I would like to propose disabling them completely. The e2es we copied from aws already do this.

It's not a significant gain, but it cuts off about 15-20 seconds from time spent building apps.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1d310d2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[pkg-pr-new]

Open in Stackblitz

pnpm add https://pkg.pr.new/@opennextjs/cloudflare@421

commit: 1d310d2

[vicb]

I agree it's worth running those each time.

Maybe running them "sometimes" can have some value (locally vs CI, first day of the week, randomly).

WDYT

[james-elicx]

I agree it's worth running those each time.

Maybe running them "sometimes" can have some value (locally vs CI, first day of the week, randomly).

WDYT

I think it would make more sense to run them as part of the lint/ts:check/format workflow if we want to keep them instead of relying on the app build