Debugging feature request: marker comments in output

[TehShrike]

It's been talked about in Gitter, but I couldn't find an issue for it yet:

debugging Svelte output in bundles would be way easier if each component had marker comments around its code indicating which component the code belonged to.

This would make it easier to Cmd+F for the code you wanted, and reduce the amount of thinking you'd have to do to find out which component this create_main_fragment function belonged to.

[Rich-Harris]

Yes, I've been meaning to do this. Good idea

[Rich-Harris]

Related suggestion from Gitter — include a comment showing the version of the compiler

[TehShrike]

Does #853 really close this? I'm just going by the changes to the test output - I didn't see component name anywhere

[Rich-Harris]

@TehShrike it uses options.filename if available, like

/* /path/to/project/components/Thing.html generated by Svelte v1.39.3 */

options.filename isn't present in the tests, but it is if you're using a bundler integration. Though I'm wondering about maybe making it relative to process.cwd(), so it's more like this:

/* components/Thing.html generated by Svelte v1.39.3 */

[TehShrike]

Oh, brilliant. process.cwd() sounds like a good idea to me, but filename alone will help immensely for the vast majority of the cases where I'm looking at the output.