Temporary sourcemaps support

[ikenfin]

Description

As a developer of vite-plugin-sentry i've seen many feature requests from users to add option to delete sourcemaps after they become uploaded to external service (Sentry in my case). issue

While there are exist some workarounds, i think better solution would control sourcemaps generation and cleaning processes at Vite level.

Suggested solution

I think it would be perfect to have some option to generate sourcemaps temporary.

// Example of config:
build: {
  sourcemap: 'hidden',
  sourcemapTemporary: true // by default false 
}

When sourcemapTemporary is false - there are no any changes in Vite behavior.
When sourcemapTemporary is true - Vite runs as always. At the end of bundling process, Vite removes generated sourcemaps (option is ignored if sourcemap was false).

Alternative

For now there are several possible workarounds (from better to worst):

1. Using CI like Jenkins to skip sourcemap files
2. Manual removing by using rimraf or similar tool (vite build && rimraf dist/**/*.map)
3. Providing plugin level option to remove sourcemaps (most sourcemap uploaders implemented in this manner at the moment).

Additional context

No response

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.

[bluwy]

3. Providing plugin level option to remove sourcemaps (most sourcemap uploaders implemented in this manner at the moment).

With the generateBundle hook, you should be able to do that? e.g.

generateBundle(_, bundle) {
  for (const file in bundle) {
    if (file.endsWith('.map')) {
      delete bundle[file]
    }
  }
}

[ikenfin]

@bluwy Thanks, this looks better than manual removing, but is'nt that solution strips out sourcemaps before next plugin run?

My idea was to provide generated sourcemaps to each plugin, no matter in which order it was added, and delete them at bundling finish.

[bluwy]

You can use enforce: 'post' or the order: "post" so that your plugin runs near the end. So I don't think it would be an issue.

[ikenfin]

So I don't think it would be an issue.

But it is - multiple plugins can use same technique with enforce and order usage. My initial request was about providing some safe way to use sourcemaps in multiple plugins while building, without worrying of their ordering or internal implementation. Like adding && rimraf but using more native way

[bluwy]

We won't add a new option if it can already be achieved by a plugin. There are more plugins that do a lot more similar stuff, and it had worked so far, so it's not an issue.

[ikenfin]

Yes, this can be achieved at plugin level, but this is requiring from user to strongly follow plugins order and enable sourcemap deletion only for last one. Anyway i got you, seems like better solution for now is to recommend users to use separate sourcemap remover plugin