You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the node bindings are using an outdated version of neon (0.8) but these don't work with the newer node ( it is sticked at node 16)
One problem is that the type that we can wrap needs to be Send, which is not the case for the type used by the slint-interpreter because we use Rc all over the place.
Since the API changed a lot, we should consider if we should switch from neon to something like https://napi.rs/
Hopefully both crates now allow to hold "persistent" handle so we can get rid of our Persistent context hack.
The text was updated successfully, but these errors were encountered:
Newer Windows images in GitHub also come with a newer version of Visual Studio (2022), which in turn breaks the neon build, because via its package-lock.json it pins a version of neon-gyp that doesn't know that VS 2022 exists (yet). For now I'll disable the node bindings build on Windows in #1446, but this is yet another argument in favor of upgrading.
Right now the node bindings are using an outdated version of neon (0.8) but these don't work with the newer node ( it is sticked at node 16)
One problem is that the type that we can wrap needs to be Send, which is not the case for the type used by the slint-interpreter because we use Rc all over the place.
Since the API changed a lot, we should consider if we should switch from neon to something like https://napi.rs/
Hopefully both crates now allow to hold "persistent" handle so we can get rid of our Persistent context hack.
The text was updated successfully, but these errors were encountered: