-
Edge bundling (Astro + Netlify adapter)
- Limitation:
astro builddoes not emit the final.netlify/edge-functions-distbundle; only the Netlify build phase produces it. This makes “prebuild +deploy --no-build” unreliable for attaching Edge Functions. - Suggestion: Provide a documented, supported way to generate the edge bundle alongside
astro build(or an explicitnetlify edge:bundle/edge:deploythat attaches prebuilt bundles without a full build).
- Limitation:
-
Deploy CLI outputs (permalink vs deploy URL)
- Limitation:
netlify deploy --jsonconsistently returns the per‑deploy URL (e.g.https://<id>--<site>.netlify.app) but not a stable permalink/primary domain URL. Theurlfield is inconsistent and not documented as canonical. - Suggestion: Always include canonical site/permalink URLs in the JSON result, and document the fields clearly (e.g.
primary_url,alias_url).
- Limitation:
This document summarizes the issues we’re seeing when running Redwood SDK (rwsdk) with Vite dev + workerd SSR in a project using LiveStore. It groups the problems by area, provides concrete evidence (errors, file references), root‑cause analysis, and upstream solution ideas for the Redwood team.
Scope: Vite 7.x, @cloudflare/vite-plugin, [email protected], dev SSR runner targeting a worker-like (workerd) environment.
| import { Chunk } from '@livestore/utils/effect' | |
| const textEncoder = new TextEncoder() | |
| /** | |
| * Configuration describing how to break a chunk into smaller payload-safe chunks. | |
| */ | |
| export interface ChunkingOptions<A> { | |
| /** Maximum number of items that may appear in any emitted chunk. */ | |
| readonly maxItems: number |
| // @ts-check | |
| const corsHeaders = { | |
| 'Access-Control-Allow-Methods': 'GET,HEAD,POST,OPTIONS,DELETE', | |
| 'Access-Control-Max-Age': '86400', | |
| } | |
| const handleEvent = async (event) => { | |
| const request = event.request |
A TypeScript script that analyzes the lines of code (LOC) growth of a Git repository month by month using cloc's git-aware functionality.
- 📈 Monthly LOC tracking over any time period
- 🎯 Git-aware analysis - no need to checkout commits
- 🚀 Language breakdown - see which languages grow over time
- 📊 Terminal visualization with ASCII bar charts
| import { describe, expect, it } from 'vitest' | |
| /** | |
| * Test Architecture - Effect RPC between 2 Durable Objects | |
| * | |
| * ┌─────────────┐ HTTP ┌─────────────────┐ | |
| * │ Test Client │ ──────────▶ │ Worker (router) │ | |
| * │ (vitest) │ └─────────────────┘ | |
| * └─────────────┘ │ | |
| * │ routes to DOs |
| /** | |
| * AI Agent Client-DO Example | |
| * | |
| * This example demonstrates how a client-do can be used to create a lightweight AI agent | |
| * that maintains conversation state, handles user interactions, and manages AI responses. | |
| * The DO acts as a stateful agent instance that persists conversation history and context. | |
| * | |
| * Architecture Overview: | |
| * ┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐ | |
| * │ Web Client │ │ Mobile App │ │ API Client │ |
| #!/usr/bin/env bun | |
| import { Effect, Logger, LogLevel } from '@livestore/utils/effect' | |
| import { Cli, PlatformNode } from '@livestore/utils/node' | |
| import { cmd, cmdText } from '@livestore/utils-dev/node' | |
| import { Schema } from '@livestore/utils/effect' | |
| // Types for our dependency update workflow | |
| const PackageUpdate = Schema.Struct({ | |
| name: Schema.String, |
This document outlines the process for updating NPM dependencies in the LiveStore project. We use pnpm update as our primary tool with syncpack for validation. Update all dependencies across the entire monorepo.
# 0. Update PNPM itself first
pnpm --version # Check current version
pnpm view pnpm version # Check latest version