Try to install that stack, delete the dependencies and rebuild it, it should work for telemetry case
yendrisrogelio
silverdr
Well, I did npm install upfront. Was kind-of expecting that things needed for the example to work would already be present in package.json so the initial impression was that it might be something deeper. After adding it there the error is in fact gone. Checking further.
0
silverdr
Mine are:
$ elixir --version
Erlang/OTP 24 [erts-12.1.5] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] [jit]
Elixir 1.13.0 (compiled with Erlang/OTP 24)
and I need these due to some dependencies breaking on earlier versions. It does not complain on the “linux” branch though.
0
yendrisrogelio
In this case I already fixed that error, I added it to the package.json and it was uploaded to github
0
yendrisrogelio
For now it was only an educational exercise, with the idea of helping people who wanted to see how to make the integration of the different tools possible.
However, the objective is met because the telemetry error is on the backend side and does not hinder the integration of svelte with phoenix 1.6. If you want to see it running, you could install the aforementioned stack using the asdf plugin that allows you to install different versions without damaging other projects.
0
silverdr
Thank you for that. The integration part is exactly what I am/was looking for. Still need to do more thorough checking but on the surface the linux-tailwind works as expected and recompiles Svelte stuff on the fly. And faaast too! 
1
yendrisrogelio
silverdr
@nikokozak Yes – thank you – every little bit counts! I still haven’t migrated the project in question to 1.6, but this surely will be of help. Thanks for taking time to post information here.
P. S. I noticed you “loosely” based it on Sveltex, which I found not to be up to snuff for some use cases, but that’s another, only “loosely” related story
1