Remove platform integration documentation (Slack, Discord, Telegram, Teams) #277
Conversation
- Delete Slack integration documentation file Co-Authored-By: bchristopher@agentuity.com <bchristopher@agentuity.com>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
docs | 05008c2 | Sep 01 2025, 08:58 PM |
WalkthroughRemoves Twoslash integration and related UI/CSS across the app, reverts MDX code-block customization to defaults, updates a docs code fence to plain TypeScript, deletes the Slack integration doc page, and cleans up Next.js config and package dependencies accordingly. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Suggested reviewers
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 💡 Knowledge Base configuration:
You can enable these sources in your CodeRabbit configuration. 📒 Files selected for processing (2)
💤 Files with no reviewable changes (2)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
✨ Finishing Touches
🧪 Generate unit tests
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
Co-Authored-By: bchristopher@agentuity.com <bchristopher@agentuity.com>
Co-Authored-By: bchristopher@agentuity.com <bchristopher@agentuity.com>
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
app/api/search/route.ts (1)
4-4: Scope nit: unrelated to “remove platform integrations.”This runtime change seems orthogonal to the docs cleanup. Either add a note to the PR description explaining the motivation/risk assessment, or split into a tiny follow-up PR.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (1)
app/api/search/route.ts(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Workers Builds: docs
🔇 Additional comments (2)
app/api/search/route.ts (2)
4-4: LGTM on moving this route to Edge.Exporting
runtime = "edge"for this handler is valid in Next.js App Router and should improve cold starts. No functional changes otherwise.
4-4: Integration references: Regex checks in content/ and app/ found no Slack/Discord/Telegram/Teams mentions or links to removed integration docs.
Lockfile: package-lock.json shows broad dependency version bumps (e.g. esbuild → 0.24.2); verify these updates are intended.
| import { source } from '@/lib/source'; | ||
| import { createFromSource } from 'fumadocs-core/search/server'; | ||
|
|
||
| export const runtime = "edge"; | ||
|
|
||
| export const { GET } = createFromSource(source); |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Confirm Edge runtime compatibility of fumadocs search.
Please verify that fumadocs-core/search/server and @/lib/source do not rely on Node-only APIs (fs, path, Buffer, crypto Node, process). If not Edge-safe, revert to Node or switch to an Edge-safe entrypoint if the library provides one.
Contingency diff if incompatibilities surface:
-export const runtime = "edge";
+export const runtime = "nodejs";🌐 Web query:
Does "fumadocs-core/search/server" support running under the Next.js Edge Runtime?
💡 Result:
Short answer: No — the fumadocs-core search/server (the built-in Search API route) is not compatible with the Next.js Edge Runtime. It requires a Node/server runtime (access to filesystem/Node APIs) and Fumadocs docs explicitly note it doesn't work on the Edge runtime. [1][2][3]
References
- Fumadocs manual/deploy docs (Cloudflare note: "Fumadocs doesn't work on Edge runtime"). [1]
- Next.js forum / community discussion confirming fumadocs can't run on Edge (search API / filesystem issues). [2]
- Fumadocs homepage example showing createFromSource(...) for a server GET handler (server/runtime expectation). [3]
Switch runtime to nodejs for the Search API.
fumadocs-core/search/server depends on Node-only APIs (fs, path, etc.) and isn’t Edge-runtime compatible—update to a Node runtime.
-export const runtime = "edge";
+export const runtime = "nodejs";📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import { source } from '@/lib/source'; | |
| import { createFromSource } from 'fumadocs-core/search/server'; | |
| export const runtime = "edge"; | |
| export const { GET } = createFromSource(source); | |
| import { source } from '@/lib/source'; | |
| import { createFromSource } from 'fumadocs-core/search/server'; | |
| export const runtime = "nodejs"; | |
| export const { GET } = createFromSource(source); |
🤖 Prompt for AI Agents
In app/api/search/route.ts around lines 1 to 6, the file currently sets export
const runtime = "edge" but fumadocs-core/search/server uses Node-only APIs;
change the runtime value to "nodejs" (replace "edge" with "nodejs") so the route
runs in the Node runtime and keep the existing export of GET from
createFromSource(source) unchanged.
…encies - Remove fumadocs-twoslash imports and usage from Code.tsx component - Remove twoslash transformers and Popup components from page.tsx - Remove fumadocs-twoslash CSS import from global.css - Convert twoslash code block to regular TypeScript in test.mdx - Remove serverExternalPackages from next.config.mjs This resolves Node.js built-in module conflicts with Cloudflare Workers Edge runtime. Local build now passes successfully with all 35 pages generated. Co-Authored-By: bchristopher@agentuity.com <bchristopher@agentuity.com>
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (3)
app/docs/[[...slug]]/page.tsx (1)
10-10: Remove commented Twoslash UI import.Dead/commented import should be deleted to prevent drift.
Apply:
-// import { Popup, PopupContent, PopupTrigger } from "fumadocs-twoslash/ui";components/Code.tsx (2)
4-5: Delete commented Twoslash imports.Keep the file lean and avoid stale references.
-// import { transformerTwoslash } from "fumadocs-twoslash"; -// import { Popup, PopupContent, PopupTrigger } from "fumadocs-twoslash/ui";
17-31: Normalize language and avoid preloading all Shiki languages (perf + resilience).
- Strip “twoslash” tokens from fences like ```ts twoslash.
- Don’t preload every language; load only what’s needed to reduce cold start/memory.
export async function Code({ code, lang = "ts", }: { lang?: string; code: string; }) { - const highlighter = await getSingletonHighlighter({ - langs: Object.keys(bundledLanguages), - themes: ["vesper"], - }); + const normalizedLang = (lang || "ts").split(/\s+/)[0]; + const languagesToLoad = (normalizedLang in bundledLanguages ? [normalizedLang] : ["ts"]); + const highlighter = await getSingletonHighlighter({ + langs: languagesToLoad, + themes: ["vesper"], + }); - const hast = highlighter.codeToHast(code, { - lang, + const hast = highlighter.codeToHast(code, { + lang: normalizedLang, themes: { light: "vesper", dark: "vesper", }, defaultColor: false, transformers: [ createStyleTransformer(), ], });Also applies to: 22-24
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (5)
app/docs/[[...slug]]/page.tsx(1 hunks)app/global.css(0 hunks)components/Code.tsx(1 hunks)content/docs/Cloud/test.mdx(1 hunks)next.config.mjs(0 hunks)
💤 Files with no reviewable changes (2)
- app/global.css
- next.config.mjs
✅ Files skipped from review due to trivial changes (1)
- content/docs/Cloud/test.mdx
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-07-23T12:40:13.980Z
Learnt from: CR
PR: agentuity/docs#0
File: .cursor/rules/mdx.mdc:0-0
Timestamp: 2025-07-23T12:40:13.980Z
Learning: This is MDX so some react components can be used
Applied to files:
app/docs/[[...slug]]/page.tsx
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Workers Builds: docs
🔇 Additional comments (1)
app/docs/[[...slug]]/page.tsx (1)
10-10: No leftover Twoslash/Popup usage or Slack links found. All code fences, MDX components, and documentation links have been removed.
- Remove fumadocs-twoslash and twoslash from package.json dependencies - Update package-lock.json to remove all related packages - This should resolve Node.js built-in module conflicts with Cloudflare Workers Edge runtime - Local build continues to pass with all 35 pages generated successfully Co-Authored-By: bchristopher@agentuity.com <bchristopher@agentuity.com>
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
package.json(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Workers Builds: docs
| "react": "^19.0.0", | ||
| "react-dom": "^19.0.0", | ||
| "twoslash": "^0.2.12" | ||
| "react-dom": "^19.0.0" |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
No-op react-dom change; verify lockfile churn and residual Twoslash/platform refs.
The version remains ^19.0.0, so this should be a no-op. Please confirm package-lock.json didn’t re-resolve unrelated trees and that Twoslash deps and Slack/Discord/Telegram/Teams references are fully removed.
- Consider adding an “engines” field to pin supported Node versions (e.g., >=18.18 or 20+) to match Next 15 requirements and reduce CI/environment drift.
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "== package.json declared versions =="
jq -r '.dependencies | {react, "react-dom": .["react-dom"], next}' package.json
if [ -f package-lock.json ]; then
echo "== Root deps recorded in package-lock =="
jq -r '.packages[""].dependencies | {react, "react-dom": .["react-dom"], next}' package-lock.json || true
echo "== Ensure no Twoslash packages remain in lockfile =="
rg -n 'twoslash|fumadocs-twoslash' package-lock.json || echo "OK: no twoslash in lock"
fi
echo "== Search repo for Twoslash remnants (imports, options, code fences) =="
rg -nP --hidden --glob '!**/package-lock.json' '(twoslash|fumadocs-twoslash|transformerTwoslash|rehypeCodeOptions|twoslash\.css)' || echo "OK: no twoslash refs"
echo "== Search for removed platform docs/links =="
rg -nP --hidden 'content/docs/.+(Slack|Discord|Telegram|Teams)|/Integrations/(slack|discord|telegram|teams)' || echo "OK: no platform doc paths"
echo "== Search MDX fences still using `twoslash` flag =="
rg -nP '^```[a-z0-9]+\s+twoslash' || echo "OK: no twoslash fences"Length of output: 1918
Lockfile unchanged—remove Twoslash remnants
- Delete commented
fumadocs-twoslashimports incomponents/Code.tsx(lines 4–5) andapp/docs/[[...slug]]/page.tsx(line 10). - Optional: add an
enginesfield (e.g.>=18.18or>=20) to match Next.js 15 and prevent CI/environment drift.
🤖 Prompt for AI Agents
package.json (around line 17) and two frontend files: components/Code.tsx (lines
4–5) and app/docs/[[...slug]]/page.tsx (line 10): remove the leftover commented
fumadocs-twoslash import lines from those two files (delete the two commented
import lines in Code.tsx and the single commented import in page.tsx), ensure no
other twoslash remnants remain, commit the removals, and run the app/build to
verify no references remain; optionally add an "engines" field to package.json
(e.g. "engines": {"node": ">=18.18"} or ">=20"} ) to match Next.js 15 and
stabilize CI/environment.
components/Code.tsx
Outdated
| import { createStyleTransformer } from "fumadocs-core/server"; | ||
| import { transformerTwoslash } from "fumadocs-twoslash"; | ||
| import { Popup, PopupContent, PopupTrigger } from "fumadocs-twoslash/ui"; | ||
| // import { transformerTwoslash } from "fumadocs-twoslash"; |
There was a problem hiding this comment.
remove instead of comment the line
app/api/search/route.ts
Outdated
| import { source } from '@/lib/source'; | ||
| import { createFromSource } from 'fumadocs-core/search/server'; | ||
|
|
||
| export const runtime = "edge"; |
There was a problem hiding this comment.
we didn't have this before... i'm worried this will break cloudflare worker
- Remove 'export const runtime = edge' from search route (jhaynie concern about Cloudflare Workers) - Remove commented import lines from Code.tsx and page.tsx instead of leaving as comments - Local build continues to pass with all 36 pages generated successfully Co-Authored-By: bchristopher@agentuity.com <bchristopher@agentuity.com>
|
Closing due to inactivity for more than 30 days. Configure here. |
Remove platform integration documentation (Slack, Discord, Telegram, Teams)
Summary
This PR removes all documentation for third-party platform integrations as part of a comprehensive cleanup effort across all Agentuity repositories. The main change is the complete removal of the Slack integration documentation file (
content/docs/Integrations/slack.mdx).This change is part of a coordinated effort to remove all mentions and integrations of Slack, Discord, Telegram, and Teams from the Agentuity codebase, as these platform integrations are being discontinued.
Review & Testing Checklist for Human
Notes
This PR is part of a larger initiative to remove platform integrations from Agentuity. Related PRs should be created for the
agentuity/appandagentuity/catalystrepositories to ensure complete removal across the entire codebase.Link to Devin run: https://app.devin.ai/sessions/16fa50cdfb07432fa57ad865c870667d
Requested by: bchristopher@agentuity.com
Summary by CodeRabbit