fix: set moduleResolution to nodenext for nextjs tsconfig

[cprussin]

No description provided.

[changeset-bot]

🦋 Changeset detected

Latest commit: c747b54

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

This PR includes changesets to release 1 package

Name	Type
@cprussin/tsconfig	Major

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

[cprussin]

Future notes to self:

As it turns out, there are still some issues with nodenext in a bundled environment.

The core of the problem is basically:

• Bundlers (including swc) have an interop mode where they hoist exports under the .default key up to the root of the module if the .__esModule property is set on a cjs module.
• Typescript follows Node's resolution strategy when using nodenext (that's the purpose of the setting after all), and in particular this means it does not hoist regardless of the presence of .__esModule.
• Next.js doesn't expose any way to set swc options, or any way to set noInterop to disable the interop behavior.

As a result, there's a bunch of places you need to add .default to make typescript work, but at runtime the hoisting makes the .default break.

Possible fixes here could be:

• Next.js exposes option to set swc's noInterop option (most realistic)
• Upstream modules distribute ESM (and declare themselves so -- if modules don't set "type": "module" in their package.json then we'll still have issues) or avoid default exports (most ideal but least realistic)
• Typescript exposes some option to enable a partial nodenext that enforces extensions & full paths but still enables interop (least ideal)