Ross MacPhee

First time commenter here on both GitHub and Angular, so please be kind 😄 I agree that Angular should be able to determine whether or not an input should be...

> @rossyman Great solution. But `` does not work. It's `false`. You should change the setter like that: > > ```ts > set: function(booleanAttribute: boolean | unknown): void { >...

I believe this is as a result of FlipperKit not being linked during release builds: https://github.com/facebook/flipper/issues/976#issuecomment-659416957 What solved this for me, was following the upgrade guide to 0.71.1 and utilising...

I'll take a look into this and see what we can do

After looking into this further, `vite-jest` is still in it's POC phase, meaning they're still in early development and most likely need to iron out some issues before adoption. Let's...

After even more investigation, here are a few points I've found: - We use `svelte-jester` to transform our `.svelte` components into Jest readable code. - `svelte-jester` requires `^v26` of Jest,...

Opened a related issue in `vite-jest` to query how we could add svelte specific support in co-ordination with our current transformer setup with `svelte-jester`: - https://github.com/sodatea/vite-jest/issues/15

`babel-plugin-transform-vite-meta-env` works nicely -- This handles all of the vite specific import stuff. With regards to the test component harness, I'd be dubious as to whether including that in the...

Raising a PR to implement the Vite specific transformations, beyond this will depend on the outcome of https://github.com/sveltejs/kit/issues/1485 For now, the solution to using sveltekit runtime modules appears to be...

> [facebook/jest#9430](https://github.com/facebook/jest/issues/9430) makes several references to `import.meta`. Is it still not available now that we're running with ESM? Or is the issue that the stuff Vite sticks there isn't being...