Runtimes map to incorrect source files in source maps

🐛 bug report

Currently whenever a runtime asset gets created it maps to the runtime plugin in the sourcemap instead of the actual runtime asset.

The reason I’ve opened this issue is to provide some more context and figure out a proper solution for this as it’ll require some reworking in the core logic of runtimes and/or asset requests

Example:

🤔 Expected Behavior

Should map to the runtime’s generated code.

😯 Current Behavior

Maps to the source code of the runtime plugin

💁 Possible Solution

I’ve got 2 ideas on how to fix this:

• Allow returning a sourcemap in the runtime plugin or generate one in applyRuntimes, both is currently impossible as AssetRequestInput has no sourcemap value.

• Implement some layer of virtual fs and create the files virtually.

🔦 Context

Trying to fix the remaining source map bugs

💻 Code Sample

import parcel from 'url:./parcel.webp';

console.log('test');

🌍 Your Environment

Current v2 branch

[devongovett]

I like the idea of returning a source map from runtimes as part of assetrequestinput. But in most cases the source map should basically be an empty map that’s 1:1 with the code, so maybe in the transformer when AssetRequestInput has a code property it could automatically generate an empty map if none is available?

[cdll]

this issue is still in v1 version~