atanda rasheed

Thank you for the information. I did forget there is a target option because I rarely used it😅. Provide/inject should fix this issue and it’s more appropriate here.

This issue is fixed by #1064

I can confirm that using `defineComponent` works instead. See, [Preview NS](https://stackblitz.com/edit/nativescript-vue3-beta-zfqncx?file=app/components/Details.vue). I'm not sure why the variant of SFC is not working 🤔

Not destructuring the props actually works; ```ts import { watch } from 'nativescript-vue'; const props = defineProps({ text: String, }); watch( () => props.text, () => { console.log("This watch should...

Exactly. It's going to be a game changer if this feature gets supported.

> I'm not sure this is the right approach for this issue, we need to support workspace folders/multiple root projects(like expert) that might be running on different elixir/erlang versions I...

> There are other issues that won't be fixed unless we manage to get the right environment here, for example if you use rustler then the project compilation will fail...

Reading your comment [here](https://github.com/elixir-lang/expert/pull/93#issuecomment-3239428325) really helped me to understand your points better. > I think this may cause issues is if two engines are trying to be built(either because you...

@mhanberg, I don't think copying to a temporary folder is efficient, considering how large some projects can be. Regardless, I already updated the implementation to pick the current versions specified...

> We would copy the engine source code, not your project source code. This is clear. My only concern is how fast this would pollute the filesystem, where every project...