* First sweep packages + some minor tweaking
* Second sweep
* Regenerate lockfile + package.json mods
* Regenerate lockfile again
* Fix CI
* Fix CI again
* All building properly
* unblock
* Tweak examples
* Comments + readme + fix rotten unit test
* switch from yarn to pnpm
* Remove full-nym-wasm (#6796)
* Remove nym-browser-extension (#6798)
* Remove nym-browser-extension
* remove unused from makefile
* Remove Node tester (#6800)
* Remove dom-utils (#6801)
* gh-actions: remove pnpm version
* nuke dist and pkg
* add missing dependency
* set node version to 24 and pnpm version to 11
* upgrade lock file from pnpm version 9 to 11
* pnpm add approved builds
* yarn -> pnpm
* upgrade jest version
* yarn -> pnpm
* Remove unused cfg; clippy!
* pnpm: when dev mode is on, unfreeze the lock file
* pnpm approve more scripts
* pnpm syntax error
* add `pnpm i`
* disable eslint temporarily while switching to biome in later PR
---------
Co-authored-by: Mark Sinclair <mmsinclair@users.noreply.github.com>
Co-authored-by: mfahampshire <maxhampshire@pm.me>
* 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>
* [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>
* 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>
* 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>
mfahampshire