Christian Klaussner

I think peer dependencies only work on the application level. To `import` a package in a build plugin, it has to be listed in `Npm.depends`. 🙁

I've opened a feature request for this: https://github.com/meteor/meteor-feature-requests/issues/164

Good idea! I've added a note about the npm package version to the README.

Syntax errors should definitely not crash Meteor! 😅 I tested a few syntax errors in a Svelte component (missing `>` and missing closing tag) but I always get a proper...

Thanks for the suggestion, @arggh. Preprocessing isn't supported yet because I haven't found a way to implement it without considerably increasing the maintenance overhead. Unfortunately, compiler plugins can't use peer...

Yeah, I would definitely like to take a look at your setup. 🙂 Maybe we could implement something similar to `vue-meteor`, with a separate package for each language or type...

No worries! Thanks for sharing your repo. 🙂 To be honest, I was a little surprised that it even works because build plugins usually can't import/require packages from the app's...

Sorry for the delay. I finally found some time to look into how the `require` function works for build plugins. I thinks it's fine to use the npm package workaround...

Unfortunately, build plugins can't have weak dependencies on other packages, so we can't make `svelte:postcss` optional. I think PostCSS support has to be included in `svelte:compiler`, like in your fork....

Yes, there are plans (in one or two weeks). 😄 I will probably document PostCSS support as "beta" or "experimental" because of the [undocumented Meteor quirk](https://github.com/meteor-svelte/meteor-svelte/issues/15#issuecomment-489231258) that is required to...