Use relative GraphiQL asset paths

[alfonso-noriega]

WHY are these changes introduced?

No issue.

The cli-kit lint job started failing on GraphiQL asset resolution because Nx now rejects resolving files from the same project through the package export path.

WHAT is this pull request doing?

Resolve the GraphiQL favicon and stylesheet through relative require.resolve paths instead of @shopify/cli-kit/assets/... package paths.

The CLI bundle step rewrites those asset lookups, so this also updates the GraphiQL bundling plugin to recognize the new relative asset paths.

How to test your changes?

• pnpm nx run cli-kit:lint --skip-nx-cache
• pnpm nx run cli-kit:type-check --skip-nx-cache
• pnpm nx run-many --all --skip-nx-cache --target=build --output-style=stream
• pnpm nx run-many --all --skip-nx-cache --target=bundle --output-style=stream

Post-release steps

None.

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes
• I've considered analytics changes to measure impact
• The change is user-facing — I've identified the correct bump type (patch for bug fixes · minor for new features · major for breaking changes) and added a changeset with pnpm changeset add

Not user-facing; no changeset needed.

[alfonso-noriega]

• Use relative GraphiQL asset paths #8010 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.