typescript 7.0.2 is the native compiler and exports no JavaScript API, so
ts-jest and typescript-eslint cannot read it (an earlier bare-7 pin here
had to be reverted for exactly that). It comes in aliased as tsgo and does
the typechecking; typescript stays on the 6 line for the tools. tsgo
surfaced two native-compiler gaps not present under tsc 6.0.3: a JS-inference
miss on two @luxfi/utila exports (app/server), and a missing CSS side-effect
ambient declaration that also covers @luxdefi/ui's own unbuilt .tsx source
(app/explorer). Both fixed with narrow ambient declarations. 16 diagnostics
across the 11 workspace packages before and after.
Co-authored-by: Hanzo Dev <[email protected]>
Lux Bridge is core network infrastructure meant for OSS developers to
build on, so it moves from the proprietary Lux Ecosystem License
(patent-protected tier) to BSD 3-Clause — the same permissive license
the rest of the Lux core stack carries (cli, sdk, genesis). Also
unifies the seven per-package license fields (MIT/ISC/BSD mixed) onto
the one repository license. No vendored modified upstream, so no
separate NOTICE is owed; third-party deps keep their licenses through
the module graph.
The repo resolved three majors of the same set at once — 0.307.0 (via
@luxdefi/ui), 0.456.0 (the catalog, used by bridge3) and 1.16.0 (pinned
directly by explorer). Same import name, three different drawings. Every
app now takes lucide from `catalog:`, and an override collapses the
transitive copy, so one version resolves for the whole tree.
app/bridge3/app/components/icons/ was a second set wearing the first
one's clothes: avatar/bag/left-arrow/right-arrow were hand-drawn, typed
as LucideProps, off-grid (17x21, 9x16, 1019x1281) and filled rather than
stroked — three of them with `fill="white"` baked into the path, so they
were invisible on a light background and could never take the theme.
None had a consumer. Deleted; Lucide draws all four (User, ShoppingBag,
ChevronLeft, ChevronRight).
What stays in that directory is not an icon set: the Lux mark and the
third-party network marks are logos, and logos are not glyphs.
explorer also declared @heroicons/react and heroicons with zero imports
of either — a set you cannot see is still a set you can reach for.
Co-authored-by: Hanzo Dev <[email protected]>
The patch-hanzogui-exports.cjs script is the only supported way to
make `pnpm install && pnpm exec vite build` succeed against the broken
@hanzo/[email protected] publish. Swallowing its exit code with `|| true`
hides the only signal we have that the workaround stopped applying —
e.g. if a future pnpm release changes traversal semantics or upstream
republishes the SDK and the patcher trips on an unexpected layout, the
install would still report success and the failure would surface much
later at the vite build step with a confusing module-resolution error.
Verified `rm -rf node_modules && pnpm install --frozen-lockfile`
completes end-to-end with the script exiting 0
(`patched 240 package(s); fixed 41 source file(s)`). Red Phase 3 R2 nit.
The SDK now ships with @hanzo/gui + @hanzogui/{core,helpers,constants,
themes,animate,animate-presence,button,input} as direct dependencies
(moved out of the optional peerDependencies block). Phase 3 R2 starts
swapping native primitives onto Tamagui-based @hanzo/gui components,
so consumers no longer have to install those packages themselves.
Three plumbing changes make this actually bundle in a consumer:
1. scripts/patch-hanzogui-exports.cjs (vendored from lux/exchange):
the published @hanzo/[email protected] + @hanzogui/*@7.0.0 packages ship
without a populated dist/, so their package.json main/module/exports
point at folders that do not exist. The patch rewrites those entries
to point at the included src/ at install time. Root postinstall hook
runs it deterministically on every pnpm install.
2. app/bridge/vite.config.ts: alias react-native -> react-native-web,
dedupe react/react-dom/react-native-web, set TAMAGUI_TARGET=web and
__DEV__=false. Minimum viable Tamagui wiring (mirrors the wiring
lux/exchange ships in a much larger config).
3. app/bridge/package.json: add react-native-web@^0.19.0 dependency
so the alias above resolves.
Result: pnpm install in a fresh checkout produces a working build with
zero manual setup. `pnpm build` in app/bridge succeeds.
- Add packageManager field to root package.json for pnpm version
- Update workflows to handle MPC tools with mocks for CI
- Fix integration tests to handle missing dependencies gracefully
- Add E2E smoke test script for basic validation
- Update test commands to be more resilient
- Remove hard dependencies on external MPC repository
All workflows should now pass successfully in CI environment
Fix issues with abi-wan-kenobi
bridge compiles, builds, and runs (routes still removed)
auth route back in
transactions route
all routes restored
Bump @hanzo/auth to fix firebase credential handling
pnpm version
linting re-enabled and issues fixed
working version with some UI tweeks
@luxfi/ui version update
fixed page routers
zeekayandHanzo Dev