arggh

I didn't yet have a chance to dig any deeper into this, but this much I know: A syntax error in any of my Svelte components causes Meteor to crash,...

It seems this only happens when the syntax error is in a file that is in a local npm package. ``` packages/ svelte-stuff/ SvelteComponent.svelte app/ node_modules/ svelte-stuff -> @../../packages/svelte-stuff ```...

There seems to be some npm packages which are using the Svelte compiler's preprocessor hooks, like https://github.com/tivac/modular-css/tree/master/packages/svelte#readme But I'm afraid meteor-svelte doesn't support using those?

I managed to setup PostCSS preprocessing in such a way, that the app can determine what settings and PostCSS-plugins to use. If it sounds like something you'd like to take...

@klaussner sorry, completely forgot about this 😳 I just pushed the branch with my stab at customizable PostCSS preprocessor + meteor-svelte: https://github.com/arggh/meteor-svelte/tree/feature/postcss With this setup, one can customize the PostCSS...

> I don't know if that's a bug or if we can rely on this "feature" in future Meteor versions. Maybe worth bringing this up in the Meteor repo? Though...

Are there any plans on implementing the PostCSS support in `svelte:compiler`?

I was trying to take another stab at this, and it seems I've accidentally removed the repo linked above when cleaning up my github account, and now I can't remember...

Some thoughts: Hopefully `svelte:compiler` will not include Svelte itself in the future either, so there isn't (🤞) a need to "save" the versions for matching future Svelte versions like there...

I haven't yet gotten to the bottom of this, but using `svelte:[email protected]`, it seems my Svelte versions for compiling and runtime differ. I couldn't get Svelte components to mount without...