feat: add developers landing by snario · Pull Request #520 · tempoxyz/docs

snario · 2026-06-19T20:27:17Z

No description provided.

Co-authored-by: Liam Horne <1933029+snario@users.noreply.github.com> Co-authored-by: Tanishq <15674971+tanishqsh@users.noreply.github.com>

vercel · 2026-06-19T20:27:19Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
tempo-docs	Ready	Preview, Comment	Jun 20, 2026 3:22pm

socket-security · 2026-06-19T20:28:14Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Package	Supply Chain Security	Vulnerability	Quality	Maintenance
react-server-dom-webpack@19.2.6 ⏵ 19.2.5		^-15		^-45
hono@4.12.26 ⏵ 4.12.15		^-45
@iconify-json/simple-icons@1.2.77 ⏵ 1.2.79				⁺²
posthog-node@5.29.2 ⏵ 5.30.2	^-4		⁺¹
accounts@0.10.7 ⏵ 0.6.7				^-1
wagmi@3.6.14 ⏵ 3.6.4				⁺¹
@iconify-json/lucide@1.2.102 ⏵ 1.2.103	⁺¹		⁺¹	^-1
@wagmi/core@3.4.11 ⏵ 3.4.5				⁺¹
vite@8.0.16 ⏵ 7.3.2		^-17
tailwindcss@4.3.0 ⏵ 4.2.4	⁺¹		⁺¹
react@19.2.6 ⏵ 19.2.5
posthog-js@1.367.0 ⏵ 1.371.4	⁺⁶		^-13	⁺¹
waku@1.0.0-beta.0 ⏵ 1.0.0-alpha.4				⁺²
@tanstack/react-query@5.99.0 ⏵ 5.100.1	⁺¹		⁺¹	⁺⁴
abitype@1.2.4
@tailwindcss/vite@4.3.0 ⏵ 4.2.4
@vitejs/plugin-react@6.0.2 ⏵ 5.2.0
react-dom@19.2.6 ⏵ 19.2.5
ox@0.14.20 ⏵ 0.14.18	^-1			^-1
viem@2.48.0
@biomejs/biome@2.3.11 ⏵ 2.4.13	⁺¹
@playwright/test@1.58.0 ⏵ 1.59.1

View full report

socket-security · 2026-06-19T20:28:16Z

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		Obfuscated code: npm `caniuse-lite` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/unplugin-icons@23.0.1` → `npm/@vitejs/plugin-react@5.2.0` → `npm/react-server-dom-webpack@19.2.5` → `npm/vocs@2.0.10` → `npm/caniuse-lite@1.0.30001790` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/caniuse-lite@1.0.30001790`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `caniuse-lite` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/unplugin-icons@23.0.1` → `npm/@vitejs/plugin-react@5.2.0` → `npm/react-server-dom-webpack@19.2.5` → `npm/vocs@2.0.10` → `npm/caniuse-lite@1.0.30001790` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/caniuse-lite@1.0.30001790`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `caniuse-lite` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/unplugin-icons@23.0.1` → `npm/@vitejs/plugin-react@5.2.0` → `npm/react-server-dom-webpack@19.2.5` → `npm/vocs@2.0.10` → `npm/caniuse-lite@1.0.30001790` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/caniuse-lite@1.0.30001790`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `caniuse-lite` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/unplugin-icons@23.0.1` → `npm/@vitejs/plugin-react@5.2.0` → `npm/react-server-dom-webpack@19.2.5` → `npm/vocs@2.0.10` → `npm/caniuse-lite@1.0.30001790` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/caniuse-lite@1.0.30001790`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `es-module-lexer` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/waku@1.0.0-alpha.4` → `npm/react-server-dom-webpack@19.2.5` → `npm/vocs@2.0.10` → `npm/es-module-lexer@2.0.0` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/es-module-lexer@2.0.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `es-module-lexer` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/waku@1.0.0-alpha.4` → `npm/react-server-dom-webpack@19.2.5` → `npm/vocs@2.0.10` → `npm/es-module-lexer@2.0.0` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/es-module-lexer@2.0.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `playwright-core` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/@playwright/test@1.59.1` → `npm/playwright-core@1.59.1` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/playwright-core@1.59.1`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `posthog-js` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package.json → `npm/posthog-js@1.371.4` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/posthog-js@1.371.4`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `webpack` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: `?` → `npm/react-server-dom-webpack@19.2.5` → `npm/webpack@5.106.2` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/webpack@5.106.2`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

Co-authored-by: Liam Horne <1933029+snario@users.noreply.github.com> Co-authored-by: Tanishq <15674971+tanishqsh@users.noreply.github.com>

jxom · 2026-06-19T21:11:42Z

+  --color-background: #111111;
+  --color-foreground: oklch(94.66% 0 0);
+  --color-info: oklch(71.7% 0.1648 250.79);
+  --color-line: #181818;
+  --color-on-accent: #ffffff;
+  --color-positive: oklch(81.51% 0.2258 148.1);
+  --color-surface-input: #222222;
+  --color-surface-page: #0a0a0a;


should be leveraging vocs css variables for some of these, or deriving vocs css variables from these

jxom · 2026-06-19T21:12:16Z

+  --color-on-negative: #ffffff;
+  --color-on-surface-onyx: #ffffff;
+  --color-surface-block: #f5f5f5;
+  --color-surface-block-muted: #f7f7f7;
+  --color-surface-card: #ffffff;
+  --color-surface-card-elev: #ffffff;
+  --color-surface-input: #f5f5f5;
+  --color-surface-onyx: #111111;
+  --color-surface-deep: #f4f4f5;
+  --color-surface-skeleton: #e5e5e5;
+  --color-surface-panel: #f7f7f7;
+  --color-surface-page: #fafafa;
+  --color-surface-shell: #ffffff;
+  --color-line: #e5e5e5;
+  --color-line-strong: #d4d4d4;
+  --color-line-dashed: #a3a3a3;
+  --color-accent-blue: #3c66d8;
+  --color-indicator-green: #168f24;
+  --color-indicator-green-dark: #0f5f18;
+  --color-performance-tps-start: var(--color-indicator-green);
+  --color-performance-tps-mid: color-mix(
+    in srgb,
+    var(--color-indicator-green) 45%,
+    var(--color-accent-blue)
+  );
+  --color-performance-tps-end: var(--color-accent-blue);
+  --color-canvas-dot-bright: #111111;
+  --color-selection-bg: #111111;
+  --color-selection-fg: #ffffff;
+  --color-code-token-keyword: #a93ad4;
+  --color-code-token-function: var(--color-accent-blue);
+  --color-code-token-string: #167a52;
+  --color-code-token-number: #6a7500;
+  --color-code-token-comment: color-mix(in srgb, var(--color-foreground) 38%, transparent);
+  --color-code-token-punctuation: color-mix(in srgb, var(--color-foreground) 48%, transparent);
+  --color-prose-body: color-mix(in srgb, var(--color-foreground) 70%, transparent);
+  --color-prose-link-decoration: color-mix(in srgb, var(--color-foreground) 28%, transparent);
+  --color-prose-marker: color-mix(in srgb, var(--color-foreground) 35%, transparent);
+  --color-prose-quote: color-mix(in srgb, var(--color-foreground) 52%, transparent);
+  --color-prose-caption: color-mix(in srgb, var(--color-foreground) 45%, transparent);
+  --color-scrollbar-thumb: #d4d4d4;
+  --canvas-dot-rgb: 17, 17, 17;
+  --canvas-dot-alpha-base: 0.045;
+  --showcase-window-frame: var(--surface-block);
+  --showcase-window-frame-border: var(--line-strong);
+  --showcase-window-bg: var(--surface-shell);
+  --showcase-window-chrome: var(--surface-panel);
+  --showcase-window-card: var(--surface-card);
+  --showcase-window-input: var(--surface-card);
+  --showcase-window-active: var(--surface-block);
+  --showcase-window-chip: var(--surface-input);
+  --showcase-window-border: var(--line);
+  --showcase-window-border-strong: var(--line-strong);
+  --showcase-window-dot: var(--surface-skeleton);
+  --showcase-window-text: var(--foreground);
+  --showcase-window-muted: var(--foreground-secondary);
+  --showcase-window-accent: var(--accent-blue);
+  --showcase-window-accent-text: var(--on-accent);
+  --showcase-window-positive: var(--indicator-green);
+  --showcase-window-positive-bg: color-mix(in srgb, var(--indicator-green) 12%, transparent);
+  --showcase-window-warning: var(--negative);
+  --showcase-window-warning-bg: color-mix(in srgb, var(--negative) 12%, transparent);
+}
+
+@theme inline {
+  --color-background: var(--background);
+  --color-foreground: var(--foreground);
+  --color-foreground-secondary: var(--foreground-secondary);
+  --color-foreground-secondary-hover: var(--foreground-secondary-hover);
+  --color-negative: var(--negative);
+  --color-info: var(--info);
+  --color-positive: var(--positive);
+  --color-warning: var(--warning);
+  --color-on-accent: var(--on-accent);
+  --color-on-negative: var(--on-negative);
+  --color-on-surface-onyx: var(--on-surface-onyx);
+
+  --color-surface-block: var(--surface-block);
+  --color-surface-block-muted: var(--surface-block-muted);
+  --color-surface-card: var(--surface-card);
+  --color-surface-card-elev: var(--surface-card-elev);
+  --color-surface-input: var(--surface-input);
+  --color-surface-onyx: var(--surface-onyx);
+  --color-surface-deep: var(--surface-deep);
+  --color-surface-skeleton: var(--surface-skeleton);
+  --color-surface-panel: var(--surface-panel);
+  --color-surface-page: var(--surface-page);
+  --color-surface-shell: var(--surface-shell);
+
+  --color-line: var(--line);
+  --color-line-strong: var(--line-strong);
+  --color-line-dashed: var(--line-dashed);
+
+  --color-accent-blue: var(--accent-blue);
+  --color-indicator-green: var(--indicator-green);
+
+  --font-display: var(--font-hbset);
+  --font-sans: var(--font-pilat-book);
+  --font-mono: var(--font-jetbrains-mono);
+}


should be leveraging vocs css variables for a lot of these, or deriving vocs css variables from these

jxom · 2026-06-19T21:17:07Z

+:where([data-theme="light"], [data-vocs-theme="light"]) [class~="hover:bg-white"]:hover {
+  background-color: var(--foreground);
+}


as mentioned above, this should be done via changing a vocs css variable rather than dissecting css like this.

Co-authored-by: Liam Horne <1933029+snario@users.noreply.github.com> Co-authored-by: Tanishq <15674971+tanishqsh@users.noreply.github.com>

feat: add developers landing

9867ade

Co-authored-by: Liam Horne <1933029+snario@users.noreply.github.com> Co-authored-by: Tanishq <15674971+tanishqsh@users.noreply.github.com>

vercel Bot deployed to Preview June 19, 2026 20:28 View deployment

fix: route marketing landing pages

a28b517

Co-authored-by: Liam Horne <1933029+snario@users.noreply.github.com> Co-authored-by: Tanishq <15674971+tanishqsh@users.noreply.github.com>

vercel Bot deployed to Preview June 19, 2026 20:47 View deployment

fix: satisfy deployment checks

2c697df

Co-authored-by: Liam Horne <1933029+snario@users.noreply.github.com> Co-authored-by: Tanishq <15674971+tanishqsh@users.noreply.github.com>

vercel Bot deployed to Preview June 19, 2026 20:55 View deployment

test: retry transient docs module load

5d46c79

Co-authored-by: Liam Horne <1933029+snario@users.noreply.github.com> Co-authored-by: Tanishq <15674971+tanishqsh@users.noreply.github.com>

vercel Bot deployed to Preview June 19, 2026 21:05 View deployment

test: retry docs client hydration setup

d4caf2d

Co-authored-by: Liam Horne <1933029+snario@users.noreply.github.com> Co-authored-by: Tanishq <15674971+tanishqsh@users.noreply.github.com>

vercel Bot deployed to Preview June 19, 2026 21:11 View deployment

jxom reviewed Jun 19, 2026

View reviewed changes

ci: run e2e against production preview

696a023

Co-authored-by: Liam Horne <1933029+snario@users.noreply.github.com> Co-authored-by: Tanishq <15674971+tanishqsh@users.noreply.github.com>

vercel Bot deployed to Preview June 19, 2026 21:18 View deployment

fix: register virtual address demo passkeys in e2e

6c3b2ce

Co-authored-by: Liam Horne <1933029+snario@users.noreply.github.com> Co-authored-by: Tanishq <15674971+tanishqsh@users.noreply.github.com>

vercel Bot deployed to Preview June 19, 2026 21:28 View deployment

merge main into developers landing

f9d2c72

Co-authored-by: Liam Horne <1933029+snario@users.noreply.github.com> Co-authored-by: Tanishq <15674971+tanishqsh@users.noreply.github.com>

vercel Bot deployed to Preview June 19, 2026 21:36 View deployment

fix: refine developers landing copy

e515124

vercel Bot deployed to Preview June 20, 2026 02:43 View deployment

fix: address theme variable review comments

55585e7

Co-authored-by: Liam Horne <1933029+snario@users.noreply.github.com> Co-authored-by: Tanishq <15674971+tanishqsh@users.noreply.github.com>

vercel Bot deployed to Preview June 20, 2026 13:48 View deployment

fix: smooth marketing page transitions

71763cd

Co-authored-by: Liam Horne <1933029+snario@users.noreply.github.com> Co-authored-by: Tanishq <15674971+tanishqsh@users.noreply.github.com>

vercel Bot deployed to Preview June 20, 2026 15:08 View deployment

Expand docs layout width

e743d68

vercel Bot deployed to Preview June 20, 2026 15:22 View deployment

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: add developers landing#520

feat: add developers landing#520
snario wants to merge 12 commits into
mainfrom
feat/developers-landing

snario commented Jun 19, 2026

Uh oh!

vercel Bot commented Jun 19, 2026 •

edited

Loading

Uh oh!

socket-security Bot commented Jun 19, 2026 •

edited

Loading

Uh oh!

socket-security Bot commented Jun 19, 2026 •

edited

Loading

Uh oh!

jxom Jun 19, 2026 •

edited

Loading

Uh oh!

jxom Jun 19, 2026 •

edited

Loading

Uh oh!

jxom Jun 19, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

snario commented Jun 19, 2026

Uh oh!

vercel Bot commented Jun 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

socket-security Bot commented Jun 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

socket-security Bot commented Jun 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

jxom Jun 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jxom Jun 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jxom Jun 19, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

vercel Bot commented Jun 19, 2026 •

edited

Loading

socket-security Bot commented Jun 19, 2026 •

edited

Loading

socket-security Bot commented Jun 19, 2026 •

edited

Loading

jxom Jun 19, 2026 •

edited

Loading

jxom Jun 19, 2026 •

edited

Loading