Output relative path

[zepfietje]

• Quick Checklist

• I have read the contributing guidelines
• I have written new tests, as applicable (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• I have added a changeset, if applicable

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

This fixes the output path to be relative as discussed in #740.

• What is the new behavior (if this is a feature change)?

Asset paths relative to Vite root.

• Does this PR introduce a breaking change? (What changes might users need to make in their application due to this
  PR?)

Maybe, maybe not: #740 (comment).

• Other information:

[changeset-bot]

⚠️ No Changeset found

Latest commit: cc82dc3

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