Mael
for the "1883 reconfigure", the thing which surprises me is that it says both "mqtts" and "1883". Shouldn't it be "8883" that it tries to reconfigure for mqtts?
@stoprocent can your library correctly handle MTU? this is a pain point I'm having with the current implementation, no clear MTU value when using webbluetooth etc
Indeed it's not so much suited for prod, but it could be a useful "reference implem" for people who want to play around with the project
Indeed, just having script that produce "broadcastable data" would be already good, and people could check the implementation that way
Cannot either attach to osX Sequoia process, or to iOS 18 (non-jailbroken) app
it seems one of the dependencies of `noble` is looking for the `process` variable which doesn't exist when using Vite (we need `import.meta.env`)
Hmmmm it's too bad that it implements a wrapper for Webbluetooth but wouldn't be available in browsers no?
If using `vite` you could just use `meta` rather than `process` to access ENV variable both in Node and browser
Hey @exaby73 so to be clear, the above linked repo is from someone else, but I have some code which doesn't require (at least not as a direct dependency) google-cloud/tasks,...
Unfortunately I don't have a sample right now, I'm trying to update all my project dependencies to latest version and I'll let you know if this fixes something