fix broken links & logger dep

Author: izadoesdev

apps/docs/app/api/ambassador/submit/route.ts

@@ -1,7 +1,7 @@
-import { createLogger } from "@databuddy/shared/logger";
+// import { createLogger } from "@databuddy/shared/logger";
 import { type NextRequest, NextResponse } from "next/server";
 
-const logger = createLogger("ambassador-form");
+// const logger = createLogger("ambassador-form");
 const SLACK_WEBHOOK_URL = process.env.SLACK_WEBHOOK_URL || "";
 const SLACK_TIMEOUT_MS = 10_000;
 
@@ -207,7 +207,7 @@ async function sendToSlack(
 	ip: string
 ): Promise<void> {
 	if (!SLACK_WEBHOOK_URL) {
-		logger.warn(
+		console.warn(
 			{},
 			"SLACK_WEBHOOK_URL not configured, skipping Slack notification"
 		);
@@ -235,7 +235,7 @@ async function sendToSlack(
 				const responseText = await response
 					.text()
 					.catch(() => "Unable to read response");
-				logger.error(
+				console.error(
 					{
 						status: response.status,
 						statusText: response.statusText,
@@ -247,13 +247,13 @@ async function sendToSlack(
 		} catch (fetchError) {
 			clearTimeout(timeoutId);
 			if (fetchError instanceof Error && fetchError.name === "AbortError") {
-				logger.error({}, "Slack webhook request timed out after 10 seconds");
+				console.error({}, "Slack webhook request timed out after 10 seconds");
 			} else {
 				throw fetchError;
 			}
 		}
 	} catch (error) {
-		logger.error(
+		console.error(
 			{
 				error: error instanceof Error ? error.message : String(error),
 				stack: error instanceof Error ? error.stack : undefined,
@@ -272,7 +272,7 @@ export async function POST(request: NextRequest) {
 		try {
 			formData = await request.json();
 		} catch (jsonError) {
-			logger.warn(
+			console.warn(
 				{
 					ip: clientIP,
 					userAgent,
@@ -290,7 +290,7 @@ export async function POST(request: NextRequest) {
 		const validation = validateFormData(formData);
 
 		if (!validation.valid) {
-			logger.info(
+			console.info(
 				{ errors: validation.errors, ip: clientIP },
 				"Form submission failed validation"
 			);
@@ -302,7 +302,7 @@ export async function POST(request: NextRequest) {
 
 		const ambassadorData = validation.data;
 
-		logger.info(
+		console.info(
 			{
 				name: ambassadorData.name,
 				email: ambassadorData.email,
@@ -319,7 +319,7 @@ export async function POST(request: NextRequest) {
 			message: "Ambassador application submitted successfully",
 		});
 	} catch (error) {
-		logger.error(
+		console.error(
 			{
 				ip: clientIP,
 				userAgent,

apps/docs/content/docs/dashboard.mdx

@@ -296,7 +296,7 @@ Discover your global audience and optimize for different regions:
   derived from the user's IP address at the beginning of a session. This
   functionality is an integral part of session tracking. Ensure `trackSessions=
   {true}` (which is enabled by default) in your [SDK
-  configuration](/docs/sdk#-configuration-options) to collect this data.
+  configuration](/docs/sdk#configuration-options) to collect this data.
 </Callout>
 
 ## Technology Stack Analysis
@@ -358,9 +358,9 @@ Track and analyze your business-specific events with detailed property breakdown
   `db.track('your_event_name', {your_properties})` method. The more relevant and
   well-structured custom events you track, the more insightful this section will
   become. For detailed guidance on how to implement custom event tracking,
-  please refer to the [SDK Methods Reference](/docs/sdk#-sdk-methods-reference)
+  please refer to the [SDK Methods Reference](/docs/sdk#sdk-methods)
   and strategies in the [Custom Event
-  Tracking](/docs/sdk#-custom-event-tracking) section of the SDK documentation.
+  Tracking](/docs/sdk#custom-event-tracking) section of the SDK documentation.
 </Callout>
 
 ### Enhanced Event Interface
@@ -557,7 +557,7 @@ Monitor your website's technical health and user experience:
   The performance metrics, including Core Web Vitals, are populated when you
   enable `trackPerformance={true}` (enabled by default) and `trackWebVitals=
   {true}` (disabled by default, but recommended) in your [SDK
-  configuration](/docs/sdk#-optional-tracking-features). Enabling these options
+  configuration](/docs/sdk#optional-features). Enabling these options
   allows the SDK to collect detailed timing and performance data from the user's
   browser.
 </Callout>
@@ -641,11 +641,11 @@ Monitor and resolve issues affecting your users:
 <Callout type="tip" title="Enabling Error Data Collection">
   To populate the error tracking sections of the dashboard, ensure you have
   `trackErrors={true}` enabled in your [SDK
-  configuration](/docs/sdk#-optional-tracking-features). This will automatically
+  configuration](/docs/sdk#optional-features). This will automatically
   capture unhandled JavaScript errors and promise rejections. For more detailed
   context on specific handled errors, you can manually send error events using
   `db.track('error', {/* custom properties */})` as described in the [SDK
-  Methods Reference](/docs/sdk#-sdk-methods-reference).
+  Methods Reference](/docs/sdk#sdk-methods).
 </Callout>
 
 ### JavaScript Error Analytics
@@ -862,7 +862,7 @@ To populate funnel data, you need to:
 1. Define the steps of your funnel within the Databuddy dashboard settings.
 2. Ensure each step corresponds to a custom event (or page view) that you are tracking with the SDK. For example, a signup funnel might be defined by a sequence of events like `viewed_signup_page` (a screen view), `started_signup_form` (custom event), and `completed_signup` (custom event).
 
-The sequence of these events for users will then build the funnel visualization. For more details on sending custom events, see the [SDK Methods Reference](/docs/sdk#-sdk-methods-reference) in the SDK documentation.
+The sequence of these events for users will then build the funnel visualization. For more details on sending custom events, see the [SDK Methods Reference](/docs/sdk#sdk-methods) in the SDK documentation.
 
 </Callout>
 
@@ -876,8 +876,8 @@ User journey visualization allows you to see the paths users take through your w
 
 <Callout type="tip" title="Data for User Journeys">
 This feature relies on the comprehensive event data tracked by the SDK. The richness of the user journeys depends on:
-- Thorough `screen_view` tracking (often automatic via `trackScreenViews={true}` in the [SDK configuration](/docs/sdk#-configuration-options)).
-- Detailed custom event tracking (`db.track()`) for significant interactions as described in the [SDK Methods Reference](/docs/sdk#-sdk-methods-reference).
+- Thorough `screen_view` tracking (often automatic via `trackScreenViews={true}` in the [SDK configuration](/docs/sdk#configuration-options)).
+- Detailed custom event tracking (`db.track()`) for significant interactions as described in the [SDK Methods Reference](/docs/sdk#sdk-methods).
 
 Each event is tied to a user's session, allowing the dashboard to reconstruct their path.
 
@@ -896,9 +896,9 @@ Richer user profiles are developed when you consistently track custom events tha
 
 Refer to these SDK documentation sections for more:
 
-- [Custom Event Tracking](/docs/sdk#-custom-event-tracking) for strategy.
-- [Standard Event Reference](/docs/sdk#-standard-event-reference) for common event types.
-- [SDK Methods Reference](/docs/sdk#-sdk-methods-reference) for `db.track()` and `db.setGlobalProperties()`.
+- [Custom Event Tracking](/docs/sdk#custom-event-tracking) for strategy.
+- [Standard Event Reference](/docs/sdk#standard-events) for common event types.
+- [SDK Methods Reference](/docs/sdk#sdk-methods) for `db.track()` and `db.setGlobalProperties()`.
 - The `db.setGlobalProperties()` method can be particularly useful for adding persistent attributes to a user's profile.
 </Callout>
 

apps/docs/content/docs/getting-started.mdx

@@ -388,15 +388,15 @@ function SignupForm() {
   <Card title="API Playground" href="/api">
     Test endpoints interactively and explore query types with real data
   </Card>
-  <Card title="SDK Configuration Guide" href="/docs/sdk#-configuration-options">
+  <Card title="SDK Configuration Guide" href="/docs/sdk#configuration-options">
     Explore all SDK configuration props and options
   </Card>
   <Card title="Dashboard Guide" href="/docs/dashboard">
     Learn to navigate your analytics dashboard and its features
   </Card>
   <Card
     title="Event Tracking Deep Dive"
-    href="/docs/sdk#-sdk-methods-reference"
+    href="/docs/sdk#sdk-methods"
   >
     Master custom event tracking, SDK methods, and standard event types
   </Card>

apps/docs/scripts/validate-links.ts

@@ -7,28 +7,35 @@ import {
 } from "next-validate-link";
 import { source } from "../lib/source";
 
+type Page = InferPageType<typeof source>;
+
+const getHeadings = (page: Page): string[] =>
+    page.data.toc?.map((item) => item.url.slice(1)) ?? [];
+
+const getFiles = (): Promise<FileObject[]> =>
+    Promise.all(
+        source.getPages().map(async (page) => ({
+            path: page.file.path,
+            content: await page.data.getText("raw"),
+            url: page.url,
+            data: page.data,
+        }))
+    );
+
 async function checkLinks() {
-    console.log("🔍 Scanning URLs...");
+    const pages = source.getPages();
 
     const scanned = await scanURLs({
         preset: "next",
         populate: {
-            "docs/[[...slug]]": source.getPages().map((page) => ({
-                value: {
-                    slug: page.slugs,
-                },
+            "docs/[[...slug]]": pages.map((page) => ({
+                value: { slug: page.slugs },
                 hashes: getHeadings(page),
             })),
         },
     });
 
-    console.log(`📄 Found ${scanned.urls.size} URLs`);
-    console.log("🔗 Validating links in content files...");
-
-    const files = await getFiles();
-    console.log(`📁 Checking ${files.length} files`);
-
-    const errors = await validateFiles(files, {
+    const errors = await validateFiles(await getFiles(), {
         scanned,
         markdown: {
             components: {
@@ -43,39 +50,8 @@ async function checkLinks() {
     printErrors(errors, true);
 
     if (errors.length > 0) {
-        console.log(`\n❌ Found ${errors.length} link error(s)`);
         process.exit(1);
     }
-
-    console.log("\n✅ All links are valid!");
-}
-
-function getHeadings({ data }: InferPageType<typeof source>): string[] {
-    if (!data.toc) {
-        return [];
-    }
-    return data.toc.map((item) => item.url.slice(1));
-}
-
-async function getFiles(): Promise<FileObject[]> {
-    const pages = source.getPages();
-    const files: FileObject[] = [];
-
-    for (const page of pages) {
-        try {
-            const content = await page.data.getText("raw");
-            files.push({
-                path: page.file.path,
-                content,
-                url: page.url,
-                data: page.data,
-            });
-        } catch (error) {
-            console.warn(`⚠️  Could not read content for ${page.url}:`, error);
-        }
-    }
-
-    return files;
 }
 
 checkLinks().catch(console.error);