DEV Community: Dongsheng

svelte5plus-calendar: Zero-dependency full calendar for Svelte 5

Dongsheng — Thu, 10 Sep 2026 12:03:39 +0000

The problem

If you’re on Svelte 5, calendar UIs often mean wrapping a React-era library, accepting a heavy dependency tree, or rolling month grids yourself and stopping short of week time-grids, recurrence, and drag-resize. You want one component that feels like Google / Apple / Outlook — without dragging half of npm into the client.

What it is

svelte5plus-calendar is a full-featured, zero-runtime-dependency calendar component for Svelte 5: month, week, day, year, and agenda views, drag & drop editing, recurring events, multiple calendars, i18n, and dark mode. TypeScript-first; styles import automatically.

Docs with live examples: blackman99.github.io/svelte5plus-calendar

Source: github.com/Blackman99/svelte5plus-calendar (MIT)

npm: svelte5plus-calendar

What you get

Six views

Month (spanning multi-day bars, +N more popovers), week & day time grids, year overview, agenda list, and a resources view (rooms/people columns) for booking-style UIs.

Drag & drop

Move events across days/slots, drag all-day bars, resize from the bottom edge, drag empty space to select/create. Touch: long-press to drag, swipe to scroll.

Built-in popovers

Click an event for details (with delete); click/drag empty space for quick-create — zero config. Your callbacks replace them when provided.

Recurring events

Practical RRULE subset (FREQ, INTERVAL, COUNT, UNTIL, BYDAY incl. 2TU/-1FR, BYMONTHDAY) as strings or typed objects, plus exdates. This event and this and following edits; occurrence/series deletion.

Theming & i18n

Light / dark / auto; every color, radius, and font is a CSS custom property; 10-color event palette that adapts to dark mode. Any BCP-47 locale via Intl (no bundles); UI strings for 10 languages; locale-aware week start and clock; timeZone prop with edits converted back.

More

Multiple calendar sources with visibility and edit permissions; current-time indicator and business hours; validRange + eventOverlap={false}; ICS parseICS / toICS; custom eventContent snippets; headless exports (layoutDay, expandRecurrence, …); keyboard navigation and aria-live.

Quick start

npm install svelte5plus-calendar

Requires Svelte 5. Styles are imported automatically.

<script lang="ts">
    import type { CalendarEvent } from 'svelte5plus-calendar';
    import { Calendar } from 'svelte5plus-calendar';

    let events = $state<CalendarEvent[]>([
        {
            id: '1',
            title: 'Kickoff meeting',
            start: new Date(2026, 7, 13, 10, 0),
            end: new Date(2026, 7, 13, 11, 0),
            color: 'teal'
        },
        {
            id: '3',
            title: 'Standup',
            start: new Date(2026, 7, 10, 9, 30),
            end: new Date(2026, 7, 10, 9, 45),
            recurrence: 'FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR'
        }
    ]);
</script>

<div style="height: 640px">
    <Calendar bind:events view="week" locale="en" editable selectable />
</div>

Handle edits with rollback:

<Calendar
    bind:events
    editable
    onEventChange={async ({ event, start, end, revert }) => {
        try {
            await api.update(event.id, { start, end });
        } catch {
            revert();
        }
    }}
/>

Who it’s for

Svelte 5 apps that need a real calendar, not only a date picker
Teams that want DnD + recurrence + i18n without a React interop layer
Authors who prefer CSS-variable theming and headless layout utils

Who it’s not (yet) for

Projects stuck on Svelte 4 (this package requires Svelte 5)
Apps that need a full RFC5545 / CalDAV server stack (client component + practical RRULE subset)
Teams standardized on FullCalendar’s plugin ecosystem with sunk cost already paid

Light comparison (not a roast)

Need	Typical pick	svelte5plus-calendar angle
Battle-tested React calendar	FullCalendar	Svelte 5-native, zero runtime deps
Month-only picker	Lightweight date libs	Full views + DnD + RRULE + resources
Stay in Svelte	DIY grids	One component + docs site examples

Try it / tell us what’s wrong

We’re especially hungry for feedback on:

First-hour DX (npm install → editable week view)
RRULE edit/split edges in real product data
Gaps vs FullCalendar for your booking / scheduling use case

👉 Live docs · GitHub · npm

Comment with your current Svelte calendar approach and the one feature that would make you switch — we’ll prioritize from real replies.

OpenBot: Self-hosted multi-bot collaboration with workspace credential isolation

Dongsheng — Thu, 10 Sep 2026 11:58:03 +0000

The problem

Engineering teams want several specialized assistants - not one chat box with everyone's API keys in a shared settings page. SaaS multi-agent products often mean someone else's trust boundary. Homegrown wrappers usually skip workspace membership, audit trails, and Bot versioning.

What OpenBot is

OpenBot is an AGPL-3.0, self-hosted multi-bot collaboration system. The current implementation includes local auth + optional OIDC, workspace membership and groups, scoped API tokens, and persistent Bot identities - shipped as a SvelteKit web app, Fastify API, PostgreSQL migrations, and a Docker Compose development stack.

Personal connections support OpenAI Chat Completions, OpenAI Responses, and Anthropic Messages-compatible endpoints, with credential-safe settings and live text/action compatibility probes. Workspace model connections support shared use without sharing credentials. Capability settings record verified evidence, explicit overrides, and compatible fallback chains.

Source: github.com/Blackman99/openbot

What you get

Self-hosted, no phoning home

OpenBot sends no telemetry, analytics, or update checks. Idle instances make no outbound requests. Named volumes preserve users, workspaces, task state, and attachments across restarts.

Identity & access

First-owner setup with OPENBOT_SETUP_TOKEN, local accounts, optional OIDC (Auth Code + PKCE). Workspace API tokens with fixed scopes (me:read, bots:*, groups:*, tasks:*, events:read, ...); only SHA-256 digests persisted; audits without credential material.

Bot identities

Create Bots with purpose -> role description + system instructions, model binding, execution limits, immutable version history, permissions and discovery, archive / soft-delete with a 30-day recovery window, copy configuration, and template export.

Conversations, tasks, routing

Unified conversation list for groups and private Bot chats. In groups: @Bot for an explicit task, or routing via a built-in workspace assistant (handoff), default lead, or local profile match. Task cards support approve, reject, answer, pause, cancel, and retry; plus streaming drafts, Markdown-safe answers, and optional SVG/HTML design artifacts in a sandboxed preview.

Personal & workspace models

Protocol-explicit adapters; AES-256-GCM for keys and custom headers; provider host / scheme / private CIDR allowlists with DNS pinning; test-and-save probes.

Routines

One-shot and repeating cron schedules in the routine's own IANA time zone; cost budgets; Bot collaboration tools limited to request_input, request_approval, delegate, and handoff (Bots cannot create or escalate routines).

Ops hygiene

Restricted openbot_runtime DB role; backup/restore archives; explicit upgrades via migrate; workspace export (no secrets); soft-delete + planned purge; PWA install with network-first offline shell and nonce CSP.

Quick start

# Docker + Compose plugin
cp .env.example .env
docker compose up --build

Web: http://localhost:3000
API status: http://localhost:3001/api/v1/status

Before a non-local deploy: use unique Postgres passwords, a high-entropy setup token, OPENBOT_ALLOW_INSECURE_LOCAL_PASSWORD=false, an exact HTTPS WEB_ORIGIN, and TLS termination. Loopback bind is the default.

The optional local Node path uses Node.js 24 + pnpm 11: pnpm install, pnpm db:migrate, then run the API and web dev servers. Verify with pnpm verify.

Who it's for

Teams that must keep model credentials and chat data on infrastructure they control
Groups that want multiple specialist Bots with real membership, permissions, and audit history
Operators comfortable with Docker Compose and Postgres-backed services

Who it's not (yet) for

Anyone expecting a hosted SaaS or one-click "bring your ChatGPT team"
Single-user laptop toys that don't need workspaces, OIDC, or API tokens
Shops that need a closed-source or permissive license for linking (this is AGPL-3.0 only)

Light comparison (not a roast)

Need	Typical pick	OpenBot angle
Hosted multi-agent chat	SaaS copilots	Self-hosted; your DB and encryption key
Single-agent wrapper	Custom Lang* scripts	Persistent Bot identities, groups, tasks, routines
"Share one API key" team setup	Shared `.env`	Personal vs workspace connections; no shared secrets

Try it / tell us what's wrong

Feedback is especially useful on:

First Compose bring-up and setup-token flow
Whether Bot permissions + discovery match how you'd grant access
Provider allowlists and Anthropic + OpenAI protocol quirks in your environment

GitHub - Blackman99/openbot

Comment with your current self-hosted agent stack and the one missing piece - we'll prioritize from real replies.

svelte-json-discovery: the discovery.js JSON struct view, as a Svelte 5 component

Dongsheng — Thu, 10 Sep 2026 11:48:33 +0000

discovery.js ships one of the best interactive JSON struct viewers in the wild. If you want that UX inside a Svelte 5 app — search, diff, validate, table, accessibility — without hosting the entire Discovery toolkit, svelte-json-discovery is a standalone extraction/reimplementation.

GitHub: https://github.com/Blackman99/svelte-json-discovery
Docs & examples: https://blackman99.github.io/svelte-json-discovery/
npm: svelte-json-discovery

Install

pnpm add svelte-json-discovery
# or npm / yarn

<script>
  import { JsonViewer } from 'svelte-json-discovery';

  const data = {
    user: { id: 1, name: 'Ada' },
    tags: ['svelte', 'json'],
  };
</script>

<JsonViewer {data} expanded={2} />

Highlights

Area	What you get
Previews	Type-colored tokens; numbers with visual thousands separators; `Date` / `RegExp` / `Set` / Error / bigint / typed arrays / functions
Scale	Windowed large array
Table	Configurable object-array table with bounded “show more”
Diff	Bounded, entity-aware moves; cycle / hostile-value protection
Validate	Async/precomputed issues; optional Ajv / Zod / Valibot adapters
A11y	ARIA tree, roving tabindex, full keyboard navigation
Schema	Hover field docs from JSON Schema (title, description, enum, deprecated, …)
Theme	Light / dark / auto via `--discovery-fmt-*`

Full prop reference: docs #api and the package README under packages/svelte-json-discovery.

Monorepo layout

Path	Role
`packages/svelte-json-discovery`	Published library
`docs`	Docs site consuming the workspace package (examples = shipping code)

Credits & license

All rendering logic, styling, and UX derive from discovery.js src/views/struct/ by Roman Dvornov and contributors. This project re-implements that view as a Svelte 5 component. MIT.

Call for feedback

Still early. If you build API explorers, admin consoles, or schema-driven UIs on Svelte 5, I’d love sharp edges filed as issues — especially large payloads, diff caps, and validator adapter ergonomics.s/objects; incremental Set/Map iterators |
| Strings | Truncation, length badges, escaped vs “as text”, URL auto-link |
| Search | Cancellable key/value walk, capped results, wraparound + reveal |
| Control | Controlled paths + bind:this controller methods (expand, focus, scroll, select) |
| Inspector | Optional accessible toolbar from svelte-json-discovery/inspector |

Bring Claude Code and Codex into Feishu/Lark group chat — with permission cards

Dongsheng — Thu, 10 Sep 2026 11:38:05 +0000

If your team lives in Feishu / Lark, but coding agents live in personal terminals, you get lost context, verbal “is it OK to run that?”, and no shared session.

agent-feishu-channel bridges Claude Code and Codex sessions into a Feishu bot — a complete coding-agent workflow inside group chat.

npm: agent-feishu-channel
CLI: afc
Repo: https://github.com/Blackman99/agent-feishu-channel
Docs: https://blackman99.github.io/agent-feishu-channel/

Why this exists

Chat is where decisions happen. The agent should show up there with local-style controls: approve dangerous tools, keep sessions across restarts, and switch providers without rewiring the bot.

What it does

Dual providers: Claude or Codex; /provider per session
Permission brokering: sensitive calls become Feishu approval cards
Session persistence: survives restarts; auto-resume; /sessions and /resume
Queue & interrupt: messages queue while generating; ! interrupts
Interactive cards: streaming status and tool activity
Runtime config: /config set without restart
Context mitigation: early warnings and a 50MB hard-reset fallback

Quick start

Needs Node.js ≥ 20, a Feishu bot app at open.feishu.cn, and claude and/or codex on $PATH. Install with npm install -g agent-feishu-channel, then run afc init and fill in app_id, app_secret, and the access allowlist before running afc.

Migrating from claude-feishu-channel? The command is now afc (was cfc); state auto-renames and history is kept.

Commands and caveats

/new /stop /status /cost /context /compact /provider /mode /model /config set /project /cd /memory

Permission modes: default, acceptEdits, plan, bypassPermissions. You own Feishu credentials and the allowed_open_ids allowlist; don’t default to bypassPermissions in shared groups.

MIT. Issues: https://github.com/Blackman99/agent-feishu-channel/issues

SveltePress: Ship docs and blogs with SvelteKit — and Svelte 5 inside Markdown

Dongsheng — Thu, 10 Sep 2026 11:13:59 +0000

The problem

If your product is SvelteKit, your docs often… aren’t. You jump to VitePress (Vue) or Docusaurus (React), then maintain a second mental model for layouts, components, and deploy adapters. That’s fine for many teams — until you want interactive examples that are the same components your app uses.

What SveltePress is

SveltePress is a content-centered site builder for docs and blogs, inspired by VitePress and built on SvelteKit. You write Markdown (and Svelte), keep Kit’s full surface area (SSR, SSG, adapters, +page.server.js, hooks), and get documentation-native features on top.

Live docs & demos: sveltepress.site

Source: github.com/SveltePress/sveltepress (~532 stars, MIT)

What you get

Svelte 5 Runes in Markdown

Embed reactive components and $state islands directly in .md — tips/callouts, Twoslash hover types, no separate playground toolchain required for simple demos.

Immutable document versioning

Keep current docs at clean URLs while publishing frozen historical snapshots, with built-in version navigation and release change catalogs.

Built-in i18n

Serve multiple locales from one site: automatic prefixing, language switcher, navigation that preserves the selected version.

Search that stays out of your way

Zero-config Pagefind (client-side, multi-locale filtering, historical index freezing). Algolia DocSearch is also supported if you already live there.

Themes you can own

Default documentation theme, blog theme, or a custom theme — configuration and theme APIs are typed.

Still SvelteKit

Same routing mental model (src/routes/+page.md, layouts, etc.). Scaffold defaults to adapter-static; swap adapters when you need SSR or platform-specific deploys.

Quickstart

# Node.js ^20.19.0 or >=22.12.0; pnpm 10 recommended
npm create @sveltepress@latest
# or: pnpm create @sveltepress

cd your-project
pnpm install
pnpm dev

Docs walk through adding @sveltepress/vite to an existing SvelteKit app if you’re not starting from scratch.

Who it’s for

Svelte / SvelteKit teams who want docs or a content site without leaving the ecosystem
Projects that need versioned docs and/or multi-locale sites
Authors who want interactive Svelte examples next to prose

Who it’s not (yet) for

Teams standardized on Vue/React doc stacks with deep plugin ecosystems already paid for
Pure “Markdown → HTML with zero JS runtime” pipelines that don’t want a Kit project at all

Light comparison (not a roast)

Need	Typical pick	SveltePress angle
Vue-native docs SSG	VitePress	Same content-first feel, SvelteKit underneath
Big React docs platform	Docusaurus	Lighter Kit-native path; versioning + i18n included
Stay in Svelte	—	First-class: Runes in MD, Kit adapters, typed themes

Try it / tell us what’s wrong

We’re especially hungry for feedback on:

First-hour DX (create → first deploy)
Versioning + i18n edge cases in real multi-product docs
Gaps vs your current VitePress/Docusaurus setup

👉 sveltepress.site · ⭐ GitHub

If you ship with it, a short “who’s using” note or issue is hugely helpful. Thanks for reading.

codsh 0.22.1 — /ship grill cards wrap long questions (DeepSeek terminal agent)

Dongsheng — Thu, 10 Sep 2026 09:40:33 +0000

DeepSeek-native terminal coding agent; /ship one sentence → verified code.

0.22.1: grill card wraps long questions fully (no 2-line ellipsis clip); sync dsh packages to 0.1.5-rc.1
Install: npm i -g @deepseek-ai/dsh codsh-cli && codsh
Links: GitHub · Docs · npm codsh-cli
Not a Claude Code env wrapper.

Feedback and a star are always appreciated.