Source map files for web-extension

[avalanche1]

How can I generate Source map files for web-extension platform?
It always gets generated inline (no matter what options I set in targets in package.json - and I, of course, don't want them inline in my production build - instead I need to upload .map files to Sentry.

[avalanche1]

@mischnic I really need your help with this 🙏

[mischnic]

Looks like this is caused by these hardcoded overrides:

parcel/packages/transformers/webextension/src/WebExtensionTransformer.js

Lines 387 to 408 in de15695

	// Set environment to browser, since web extensions are always used in
	// browsers, and because it avoids delegating extra config to the user
	asset.setEnvironment({
	context: 'browser',
	outputFormat:
	asset.env.outputFormat == 'commonjs'
	? 'global'
	: asset.env.outputFormat,
	engines: {
	browsers: asset.env.engines.browsers,
	},
	sourceMap: asset.env.sourceMap && {
	...asset.env.sourceMap,
	inline: true,
	inlineSources: true,
	},
	includeNodeModules: asset.env.includeNodeModules,
	sourceType: asset.env.sourceType,
	isLibrary: asset.env.isLibrary,
	shouldOptimize: asset.env.shouldOptimize,
	shouldScopeHoist: asset.env.shouldScopeHoist,
	});

cc @101arrowz

[101arrowz]

Source maps don't actually work when they aren't inline in web extensions but we should allow this feature to be overridden when needed. Haven't been too active on maintaining webext in parcel lately but I think this should be an easy fix for anyone else.

[avalanche1]

#8530