Automatic Updating of the main property of package.json

[fireflysemantics]

Description

When vite builds for production, it postfixes a random string to the end of the bundle.

It would be nice if we could configure vite to automatically update the main field of package.json to point to bundle each time a build is run. This makes it easier to publish to NPM, as we could keep the benefits of the random string postfix.

Suggested solution

It's possible to make the bundle name fixed, but that has a few drawbacks.

Alternative

Fixed bundle file name configuration.

Additional context

Stackoverflow Question

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[hi-ogawa]

When we publish bundles to npm that use the main property package.json to indicate the bundle file ( So that the UNPKG CDN can be used) we have to update this property each time we want to publish.
(from https://stackoverflow.com/questions/79536305/hooking-into-providing-a-callback-for-vite-production-builds)

This sounds like too niche deployment scenario, so I don't think Vite would support such mechanism builtin. That said, you should be able to achieve the same by writing own script before release to update package.json manually maybe by looking up https://vite.dev/config/build-options.html#build-manifest. Please provide an minimal example project to show your current setup if you need a further help.

---

Actually, for unpkg use case, it should be probably fine to have a fixed bundle name since unpkg will add the version suffix and that should serve as cache busting, for example, https://unpkg.com/slash is redirected to https://unpkg.com/slash@5.1.0/index.js.