Joel Mukuthu

I also observed the same: https://github.com/semantic-release/semantic-release/issues/1129

The issue title was also a bit confusing, I've updated it to make it a bit clearer. While I have your attention, what does ` to throw (a|an) ` do...

@alexjeffburke I agree, but I've also always thought of `to satisfy` as an assertion that allows you to assert against different types which to me makes this an acceptable ambiguity...

Sounds good, and I agree that that's a better approach when the use-case is bundling with webpack. On the other hand, if one runs migrations manually, I'd imagine one would...

Hi @charlypoly / @dotansimha. I'm trying out the client preset and so far it's going well but I'm missing some config options that I could previously set: `useTypeImports`, `arrayInputCoercion`, `immutableTypes`,...

Hi @fabiospampinato. Sorry for commenting on a closed issue, but I've been seeing similar behaviour - I don't mind opening a new issue if needed. My .todo file has 537...

(only chiming in as a user) For me the extra typing is not an issue because I have to do a lot of it anyway while working with TypeScript. As...

I understand. Not to linger, but is it invalid syntax or more of an "undefined/unknown type" error? I'm asking because I don't know how TypeScript's compiler handles the two cases....

I may have missed this but is splitting it up an option? ```svelte import type { Foo } from './foo'; export let items: Foo[]; interface ComponentSlots {} interface ComponentEvents {}...

@dummdidumm is it possible to work on supporting `interface ComponentSlots {}` (with or without support for generics) in the meantime? Or would introducing that be contradictory to the things discussed...