fix: Vite 8 (Rolldown) compatibility for content scripts

[sheldhur]

Summary

Two fixes for Vite 8 (Rolldown) compatibility when building Chrome extensions with content scripts:

1. Duplicate refIds: this.emitFile({ type: "chunk", name: basename(file) }) returns the same refId for different files with the same basename (e.g. seller/content.tsx, cmp/content.tsx, marketplace/content.tsx). Only the first script gets its fileName resolved; the rest fail with Content script fileName is undefined.

2. Wrong MAIN world loader path: The loader uses ./${fileName.split("/").at(-1)} which loses the subdirectory, producing a broken path.

[changeset-bot]

⚠️ No Changeset found

Latest commit: a19f489

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

[sheldhur]

@Toumash can you look at this? I can update the failed tests if you're ready to merge it

[silas]

I'm not sure if it's the same issue or not (I've haven't dug into it yet), but I also had an issue where I had a content script and service_worker script both named main.ts (but in different directories), and the generated service-worker-loader.js script ended up importing the content module/file instead of the service_worker module/file.

I'm using Vite 8.

[sheldhur]

@Toumash ping

[Toumash]

i'm not sure about the subdirectory why would it need a different behavior than a line below

 : createProLoader({ fileName }),

[sheldhur]

It just works this way. If you want to see something like createProMainLoader({ fileName }) I can change createProMainLoader