- why?
when using the mixfetch SDK, i was encountering issues, when posting requests to specific endpoints. It was not parsing the response correctly with:
Error: panic:syscall/js: Value.Call: property getReader is not a function
By updating the above, i've tested this works on all variations of post and get request using mixfetch.
Locally I had to upgrade my version of go to 1.20
* adjusting ts mixnet client constructor
* added forceTls argument to 'ClientOptsSimple'
* more sdk types removed
* fixed import
* removed go debug code
* printing wasm blob version on load
* version bump
* temporarily removed 'nym/nym/wasm/full-nym-wasm'
* changed workspaces definition
* correctly setting initial rc.0 suffix
* updated crate versions
* reverted 'useWorkspaces' lerna option
* Fix up dependency versions
* Add dev mode toggle to SDK publish scripts
* Show location of WASM package
* Change dev mode and CI build order
* Bump package versions in SDK docs
* Remove two versions of `mix-fetch` from SDK docs and only use `-full-fat` version
* Remove old arguments for mixFetch and rename to bust cache
* Remove `nym-wasm-sdk` from linting
* Release v1.2.3 of Typescript SDK
* Force WSS on mixnet client
* Bump TS SDK to 1.2.4-rc.0
* Clean up lock file
* Update node-tester version to 1.2.3 in nym-wallet
---------
Co-authored-by: Mark Sinclair <mmsinclair@users.noreply.github.com>
* fix: sdk publish script
The bash implementation used in the GitHub CI runner seems to have an
issue with incrementing a variable with `(( COUNTER++ ))` while `((
COUNTER=+1 ))` works fine.
* Add more sdk packages to workspace and normalize build sdk scripts
* Disable workspaces in npm publish sdk
Signed-off-by: Sebastian Martinez <me@sebastinez.dev>
* Continue publishing even when it fails
Signed-off-by: Sebastian Martinez <me@sebastinez.dev>
---------
Signed-off-by: Sebastian Martinez <me@sebastinez.dev>
Tommy Verrall