attach the preprocess result to module meta so svelte.compile can get the dependencies and sourcemap.

should the dependencies handling be moved into this plugin instead? sourcemap in compile could be inMap then 🤔

I think it's fine to leave it as is. If I wanted to find out how dependencies were being handled, I would intuitively look at the compile plugin file rather than preprocess, so that's one reason to keep it as is.

thing is that dependencies are really a preprocessor thing, the compiler always only looks at the input svelte code and assumes it to come from one file (except the input sourcemap can reference multiple files but the compiler doesn't use that for changing the output in any way)

either way thats for a follow-up PR

Oh interesting. So it should really be in the preprocess plugin, that way if it were ever removed, you wouldn't have to fiddle with the compile file?

this used to be a style preprocessor, however that made the preprocess plugin more complicated. Just slicing it in behind the last closing style tag is much less overhead.

It could break in dev if someone were to have a literal close style tag after the actual close style tag. Is that acceptable?

<style>div{color: red}</style>
<div>{'</style>'}</div>

transform the module again so we get the output including preprocess plugin and third party plugin changes.

the previous implementation called our compile helper that preprocessed and compiled according to svelte config but that would not account for the new preprocess plugin or third party plugins.