-
Note: Opening this issue here just as a heads-up.
I don't know that I expect it to be fixed, but I did want to have raised it.
I have to support Mobile Safari 9 (internal version `601.2` in the…
-
Hi, I found some issues when using this lib in my TS project.
- pre installed 'websocket' lib needs .node c++ compiled module, it's not compatible in webpack, I tried 'ws' instead of 'websocket', and…
-
This is intended to extract an explicit discussion point about polyfilling this proposal today. A good bit of discussion about this happened in https://github.com/WebAssembly/webidl-bindings/issues/25…
-
.
-
Native Promises have started landing in places (like Chrome Canary), so the polyfill shouldn't try to stomp on global.Promises so blithely.
-
**Describe the bug**
When importing the SDK into a webpack 5 application there are underlying libraries that are no longer included as standard (for browser) which need require modifying the links to…
-
It would be very helpful to be able to select the target or targets that I care about, and cargo-unmaintained removes crates which are not used in those targets.
The output for my work monorepo inc…
-
Since the days of Node 0.x, a lot of things have changed in the Node ecosystem.
When Node was first created, a lot of useful functionality was missing from the ECMAScript standard, so Node created …
-
## Problem
According to the FAQ page:
> Webpack 5 no longer auto-polyfills some of the node modules used by this sdk. You will have to polyfill them to fix any errors regarding missing modules.
…
-
Node Buffer only works in the browser with a polyfill, it is not good practice to expect the client to have it. Also it should fix an issue we have with Cypress on tdex-app.
From my research we can u…