Shin Ogata

> The sourcemaps are now emitted as actual files before generateBundle, so your plugin could operate on those in the bundle object (by removing them and re-emitting them as assets)....

How can I know the chunk path? I couldn't find it out by following the key included in the `bundle` below. ``` [ 'exports', 'facadeModuleId', 'isDynamicEntry', 'isEntry', 'isImplicitEntry', 'moduleIds', 'name',...

> It is the fileName property Unfortunately, `fileName` doesn't seem to contain a directory path. ```js for (const key of Object.keys(bundle)) { const chunk = bundle[key]; console.log(Object.keys(chunk)); console.log(`fileName: ${JSON.stringify(chunk.fileName)}`); //...

> But that is unlikely, as it would be a problem if there were .map files that is outside rollup responsibility in that directory. Sorry I misunderstood a little. So...

> No, you should be able to do it in JavaScript in the bundle. I got it. indeed. And the temporary files are not created. But I think that it...

Thank you for information. What I want to do is create and display root for each library on inspector as follows. For that I need to adjust `sourceRoot` and `sources`...

By the way, are you going to continue this behavior change in the future? (not reflect bundle.map in `generateBundle`) I feel little bit a strange that changes in `generateBundle` are...

Ok, so what do you think that the right `hook` to patch the `source-map` created by `rollup` ? - `generateBundle` - `writeBundle` - others

I was able to make it work as expected with the following changes. ```js 'use strict'; const { relative } = require('path'); function refrect(opts, content, map) { if (!opts.sourcemap) {...

I've confirmed that the latest 4.9.3 fixes this issue. 👍