Tags · Dargon789/web-sdk

Use-React-Query-options-and-enabled-flags

Apr 9, 2026
f80a6cd
zip
tar.gz

Release-6.0.4-node-URL-fixes-&-deps-update

Apr 9, 2026
9bf0a1b
zip
tar.gz

web-sdk-fix-knip

Fix mk api link (#340)

* Adding init knip setup

* chore: remove unused immutable connector package (0xsequence#588)

---------

Co-authored-by: Corban Riley <[email protected]>
Co-authored-by: tolgahan-arikan <[email protected]>
Co-authored-by: googleworkspace-bot <[email protected]>

Mar 6, 2026
b598b49
zip
tar.gz
Immutable . This tag is bound to an immutable release and cannot be reused.
Notes

fix-update-web-sdk

Merge branch 'master' into fix-mk-api-link

Mar 6, 2026
c10f808
zip
tar.gz
Immutable . This tag is bound to an immutable release and cannot be reused.
Notes

web-sdk-main

Main (#332)

* fix: include source files in npm package for sourcemap resolution

Include TypeScript source files (.ts, .tsx) in the npm package files array
to fix sourcemap warnings in downstream projects using vitest or other tools
that try to resolve sourcemap references.

This follows the wagmi/viem approach where source files are bundled alongside
compiled output so sourcemaps can correctly point to original sources.

* chore: upgrade wagmi to 2.19.5 and viem to 2.44.4 with withCapabilities support (0xsequence#579)

* Trails into wallet widget (0xsequence#580)

* chore: upgrade wagmi to 2.19.5 and viem to 2.44.4 with withCapabilities support

* refactor swap views and remove legacy swap coin components

* update wallet widget navigation and views

* adjust sequence wallet provider utilities and analytics

* update connect package styles and types

* update wallet widget package docs and metadata

* update pnpm lockfile

* feat(hooks): move node/trails/api URLs into config env

* default theme to dark

* chore: update 0xtrails dependency to version 0.10.2

* upgrade trails

---------

Co-authored-by: Alexander Kolberg <[email protected]>

* Add Vercel Web Analytics to Next.js (#313)

# Vercel Web Analytics Installation Report

## Summary
Successfully installed and configured Vercel Web Analytics for the Next.js App Router project located in `examples/next`.

## Changes Made

### 1. Package Installation
- **Added dependency**: `@vercel/analytics@^1.4.2` to `examples/next/package.json`
- **Added dev dependency**: `@vanilla-extract/next-plugin@^2.4.6` (required by the project configuration)
- **Updated lockfile**: `pnpm-lock.yaml` with new dependencies

### 2. Analytics Integration
**File**: `examples/next/src/app/layout.tsx`

Added the Analytics component to the root layout file following Next.js App Router best practices:
- Imported `Analytics` from `@vercel/analytics/next` at the top of the file
- Added `<Analytics />` component inside the `<body>` tag, after the existing content
- Placement ensures analytics tracking is initialized properly for all pages

### Code Changes:
```tsx
// Added import
import { Analytics } from '@vercel/analytics/next'

// Added component in the body
<body className={inter.className}>
  <ThemeProvider theme="dark">
    <Providers initialState={initialState}>{children}</Providers>
  </ThemeProvider>
  <Analytics />
</body>
```

## Implementation Details

### Router Type
This project uses **Next.js App Router** (identified by the presence of `app/layout.tsx`), so the Analytics component was added to the root layout file as per Vercel's documentation.

### Package Manager
The project uses **pnpm** (confirmed by `pnpm-lock.yaml` and `packageManager` field in `package.json`).

### Dependencies Installed
- `@vercel/analytics@^1.4.2` - The main Vercel Web Analytics package
- Package was installed successfully with version 1.6.1

## Verification

✅ Package successfully installed via pnpm
✅ Analytics component properly imported from `@vercel/analytics/next`
✅ Component added to the correct location in the root layout
✅ Code syntax is correct and follows Next.js patterns
✅ All changes staged for commit

## Notes

- The Analytics component is placed inside the `<body>` tag, after the main application content
- This is a client-side component that will automatically track page views
- The component will only send data when deployed to Vercel (no data is sent in development by default)
- No additional configuration is needed for basic analytics tracking

## Additional Dependencies

Added `@vanilla-extract/next-plugin@^2.4.6` as a dev dependency because it was referenced in the project's `next.config.mjs` but was missing from the package.json.

Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>

* wallet-widget docker

* Add master branch to GitHub Actions workflow (#316)

Signed-off-by: Dargon789 <[email protected]>

* Add Vercel Web Analytics to Next.js (#314)

# Vercel Web Analytics Implementation Report

## Summary
Successfully installed and configured Vercel Web Analytics for Next.js projects in the repository.

## Changes Made

### 1. App Router Project (examples/next)
**Status:** ✅ Already configured
- The `@vercel/analytics` package was already installed (version ^1.4.2)
- The `<Analytics />` component was already imported and added to `src/app/layout.tsx`
- Placed inside the `<body>` tag after the main content providers
- No changes were needed for this project

### 2. Pages Router Project (examples/nextjs-pages)
**Status:** ✅ Configured successfully

#### Files Modified:
- **examples/nextjs-pages/package.json**
  - Added `@vercel/analytics` version ^1.4.2 to dependencies
  - Fixed pre-existing workspace dependency issue by removing non-existent `@0xsequence/kit-checkout` package

- **examples/nextjs-pages/pages/_app.tsx**
  - Added import: `import { Analytics } from '@vercel/analytics/next'`
  - Added `<Analytics />` component inside the `<Providers>` wrapper, after `<Component {...pageProps} />`

### 3. Additional Fixes
**File:** examples/react-waas/package.json
- Removed non-existent `@0xsequence/kit-checkout` workspace dependency that was blocking installation
- This was a pre-existing issue in the repository that needed to be fixed to allow `pnpm install` to complete successfully

### 4. Lock File Updates
- **pnpm-lock.yaml** was updated with all new dependencies after running `pnpm install`

## Implementation Details

### App Router (examples/next)
The Analytics component is correctly placed in the root layout:
```tsx
<body className={inter.className}>
  <ThemeProvider theme="dark">
    <Providers initialState={initialState}>{children}</Providers>
  </ThemeProvider>
  <Analytics />
</body>
```

### Pages Router (examples/nextjs-pages)
The Analytics component is correctly placed in the app component:
```tsx
return (
  <Providers>
    <Component {...pageProps} />
    <Analytics />
  </Providers>
)
```

## Testing Notes
- Dependencies were successfully installed with `pnpm install`
- Lock file (pnpm-lock.yaml) was updated
- Pre-existing build issues (cyclic workspace dependencies) prevent full build testing, but these are unrelated to our Analytics implementation
- The syntax and structure of both implementations are correct and follow Vercel's official documentation

## Package Manager
- Using **pnpm** (version 10.24.0) as specified in the repository's package.json

## Verification
All changes follow the official Vercel Web Analytics documentation:
- Correct import from `@vercel/analytics/next`
- Proper component placement in both App Router and Pages Router architectures
- Package version ^1.4.2 matches the existing App Router implementation

Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>

---------

Signed-off-by: Dargon789 <[email protected]>
Co-authored-by: Alexander Kolberg <[email protected]>
Co-authored-by: Alexander Kolberg <[email protected]>
Co-authored-by: Mithat Akbulut <[email protected]>
Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Co-authored-by: googleworkspace-bot <[email protected]>