- 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>
* Squashing all the changes
initial router
started expanding the API
initial empty openapi/swagger
populated build-info endpoint
wip: populating rest of swagger
missing swagger data + using closure capture for immutable state
running the api as a proper task in gateway 'run'
fixing some version/feature clashes
refactored routes structures
initial host information endpoint
expanded on gateway-related endpoints
signing host information
moved all models to separate crate
unified http api client
routes unification + node api client
new generic cache and refresher
nym-api caching node self described information
removed old cache type
temporarily wired up NymContractCache to NodeDescriptionProvider
caching self reported host info
clients using self-described gateway information
fixed request timeouts for wasm
fixed wasm builds
post rebase fixes
cargo fmt
brought in wg routes into nym-node router
added ErrorResponse for wireguard routes
basic swagger support for wg endpoints
turns out swagger can be happy with strongly typed requests
output type support for wg routes
using concrete error type for nym node request error
fixed the registration test
landing page configurability
increased configurability
fixed build and lints of other crates
added default user-agent to http-api-client
reduced severity of gateway details lookup failure
changed default http port from 80 to 8080
nym-api using new default port for queries
added health endpoint
nym-api trying multiple ports for the client
using camelcase for node status
corrected health endpoint description
restored and revamped 'force_tls' flag to filter all gateways that support the wss protocol
fixed 'pub_key' path param in open api schema
derived Debug on 'NymNodeDescription'
ensuring valid public ips
added init and run flags to set hostname and public ips
fixed listening address being pushed to public ip
fixed the positional local flag
logging remote ip address of the request
updated helper function to query for described gateways
enabled tls in gateway client
removed hack-opts from mix fetch
additional changes after rebasing against origin/develop
* clippy
* wasm-related target locking
* more clippy, but this time in tests
* [wasm-client] keeping ownership over 'ReceivedBufferRequestSender' channel when spawning 'ResponsePusher'
* Bump version of Typescript SDK to RC.10
* GitHub Actions workflow to publish SDK to NPM
* Bump package version manually
---------
Co-authored-by: Mark Sinclair <mmsinclair@users.noreply.github.com>
* Attempt at simplifying top-level Makefile
* Another sweep at tidying up Makefile
* Further refinements
* Remove deprecated clippy-happy and no-clippy targets
* always using port 443 for tls gateway connection
* bumping up rc version
* hack: additional hardcoded gateways
it disables topology refresh
* Add NPM packages to tool for bumping versions
* Bump RC versions of SDK packages
* Use manual gateway details
* Add progress to `publish.sh` script
* Add docs for WSS workaround
---------
Co-authored-by: Mark Sinclair <mmsinclair@users.noreply.github.com>
* js error message
* Ability to explicitly disconnect mixfetch
* removed unused import
* added disconnect method directly to sdk package
* simplifying error throw
Co-authored-by: Mark Sinclair <14054343+mmsinclair@users.noreply.github.com>
* added onunload event listener handler
* Using global instance of mixfetch to disconnect
Co-authored-by: Mark Sinclair <14054343+mmsinclair@users.noreply.github.com>
* Bump RC versions
* MixFetch, move unload handler to creation and check for undefined `window`
* Bump RC version
* Force TLS on mixFetch demo
* Add info about working around mixed content errors for mixFetch
---------
Co-authored-by: Mark Sinclair <14054343+mmsinclair@users.noreply.github.com>
Co-authored-by: Mark Sinclair <mmsinclair@users.noreply.github.com>
* Squashing commits
added forceTls argument to 'MixFetchOptsSimple'
made forceTls flag optional in mix fetch opts
whacking those moles
* GitHub Actions: install node
---------
Co-authored-by: Mark Sinclair <mmsinclair@users.noreply.github.com>
* Bug fix `mixFetch` build
* Batch integration tests for mixFetch
* Bump RC version
* Tidy up READMEs
* Bump version to RC4 and fix up a few interfaces
* Bump version to RC5 and fix opts
* NodeJS SDK
* mixFetch usage example
* Update internal dev tester readme
* Add NodeJS packages to publish script
* Update lock file
* Upgrade `lerna`
---------
Co-authored-by: Mark Sinclair <mmsinclair@users.noreply.github.com>
* changed NymConfigTemplate trait to call 'template' by reference
* network requester lib
* introduced generic parameter to 'MixTrafficController' to allow non-remote gateways
* allowing for custom gateway sender
* types cleanup
* minor gateway cmds refactor + initial NR work
* wip
* running a NR inside gateway
note: this NR isnt tied to the gateway yet
* rebase fixes
* propagating same shutdown handle
* wip
* starting NR with appropriate local transceiver
* fixed premature shutdown
* wiring up PacketRouter
* both ends wired together
* actually working
so much cleanup to do now
* started removing dead code
* wip
* temp: hardcode gateway
* further cleanup
* fixed build of other binaries
* setup-network-requester subcmd
* overriding NR config in gateway init/run
* wip making it wasm-compatible [again]
* refactored 'GatewaySetup'
* clippy and friends
* removed debug code
* rust 1.72 lints
* ensuring local gateway is available + some comments
* correctly putting network requester data in the same underlying details struct
* improved gateway errors
* changed 'network_requester_config' deserialization
* missing clap annotation for 'enabled' flag in 'setup-network-requester' command
* saving config file after 'setup-network-requester'
* removed dead code
* review comments
* make embedded NR wait for gateway to come online (for at most 70min)
* fixed shutdown on successful gateway wait
* updated NR config override
You can't specify profile in the manifest of a crate when it's part of a
workspace. Move the profile directives that cargo complains about to the
top-level workspace Cargo.toml
* wip
* post-cherry pick fixes
* wip
* wip
* using sqlite-based indexeddb shim
* running nymClient in worker thread
* improved received handling
* building node mix-fetch
* fixed mix fetch request constructor if args[1] == undefined
* fixed build target
* nodejs origin bypass
* mix fetch in node
but I dont think anyone should use it over normal client...
* target locking
* fixed post-rebasing issues
Jędrzej Stuczyński