Cristiano Aguzzi
Cristiano Aguzzi
I'm migrating an old project from `browserify` to `esbuild` and I found out that I can't override the default polyfils with some custom implementation. I'm not sure if this is...
Currently, when you are using the core package you are bound to the Scripting API interface. This limits us in experimenting with new features before "standardization" we need an extension...
> If I recall correctly those set of methods are meant to update the form generated by the binding, trying to fulfill what the user set in the `PartialTD` passed...
I discovered this memory leak a week ago, but only today I finally got what is the issue. Take this simple code: ```js const { Servient } = require("@node-wot/core"); const...
As the title says when using node-wot in a browser context (i.e., angular, vue, webpack, etc.) it's hard to configure correctly TS types. We should look at how to improve,...
Current implementation of HTTP long polling mechanism times out after 1 hour if no data is set after 1 hour. During the weekly call, we draft a few options: -...
Relevant discussion thread: https://github.com/eclipse-thingweb/node-wot/pull/1183#pullrequestreview-1769890507 (first comment then follow the discussion).
Given the recent advancement in the Discovery specification, node-wot might be a good fit for a [Readonly directory](https://github.com/w3c/wot-discovery/issues/208) and its thing description might be exposed to a well-known URL as...
The Scripting API defines a [Expand Thing Init](https://w3c.github.io/wot-scripting-api/#expand-an-exposedthinginit), but currently, our `ExposedThing` stops at step 3. We should align it with the spec. p.s. This causes https://github.com/eclipse/thingweb.node-wot/issues/873, because the HTTP...
In some tests, we use `promisify` where the other places we use the `new Promise` pattern. Personally, I found `promisify` less verbose and more explicit, but we have to choose...