Conduitry

Nope, you're not doing anything wrong. The underlying library magic-string changed the arguments to one of its methods. The old way of calling it still works for now, but prints...

Adding a dependency on `TextEncoder` would add a requirement of Node 12, which isn't necessarily a deal-breaker, and if there isn't a more compatible way of doing this, I think...

I'm able to reproduce this with the quickstart app [here](https://www.ory.sh/hydra/docs/5min-tutorial/) by editing `quickstart.yml` to include a short value for the `TTL_LOGIN_CONSENT_REQUEST` environment variable. The logs indicate that the GET to...

This should be fixed in 3.50.0 - https://svelte.dev/repl/935dfa05c34f4158afe89fa2ea4ff601?version=3.50.0

The 'was created with unknown prop' is a runtime error, not a compile time error, and so is unaffected by the `onwarn` compiler option.

The main technical problem here is that it involves Svelte identifying template expressions written in a language that it cannot parse. The beginnings of template expressions are found via the...

If completely avoiding duplicating Svelte parser logic in a preprocessor is not a goal, this all could be fairly straightforwardly implemented in userland in a template preprocessor. The template preprocessor...

If we did integrate this into the parsing by making it an option to the compiler (rather than handling it in an earlier preprocessing step), we'd need to enforce that...

Without some understanding of the underlying language used within the `{ }`, we can't determine where the expression stops. Consider `{"}"}`, a weird but perfectly valid expression to write in...

While looking at https://github.com/UnwrittenFun/prettier-plugin-svelte/issues/70 it occurred to me that things like the string `` happening within the `` tag is something that Svelte preprocessors also have trouble with. If we've...