fix(next): avoid package.json resolver failures in loader dep tracking

[NathanColosimo]

Fixes #1087 , and I've been having this problem myself with: Bun monorepo, turbopack, nextjs, calling start() in react server action in the actions.ts file.

In monorepo + Turbopack setups, loader dependency tracking can fail with:

• TurbopackInternalError: failed to deserialize message
• nested ResolveMessage: Cannot find module '../package.json'

This comes from resolving package.json via createRequire(...).resolve(...) inside resolveLoaderStaticDependencies().

Fix:

• Stop resolving package.json through createRequire(...).resolve(...)
• Derive package.json paths from already-resolved paths
• Add them only if they actually exist.

lmk any changes!

[changeset-bot]

🦋 Changeset detected

Latest commit: e49606b

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

This PR includes changesets to release 14 packages

Name	Type
@workflow/next	Patch
workflow	Patch
@workflow/world-testing	Patch
@workflow/core	Patch
@workflow/builders	Patch
@workflow/cli	Patch
@workflow/nitro	Patch
@workflow/web-shared	Patch
@workflow/astro	Patch
@workflow/nest	Patch
@workflow/rollup	Patch
@workflow/sveltekit	Patch
@workflow/vite	Patch
@workflow/nuxt	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

[vercel]

@NathanColosimo is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

[ijjk]

Hi, this change makes sense to me

Could you sign off this commit with steps mentioned here https://github.com/vercel/workflow/pull/1192/checks?check_run_id=64907677338

[NathanColosimo]

Hi, this change makes sense to me

Could you sign off this commit with steps mentioned here https://github.com/vercel/workflow/pull/1192/checks?check_run_id=64907677338

fixed, ty

[VaguelySerious]

@NathanColosimo Could you also add a changset? (pnpm changeset) with a patch version change for @workflow/next?