dev-server
Development Server Guide
This guide covers working with the local development server and build watch monitoring.
Astro Dev Server Checklist
- Prefer the shared HTTPS server on port 4600 when available.
- When using browser automation tools (claude-in-chrome), you may need to manually accept the self-signed certificate in Chrome once before automation will work. Navigate to
https://localhost:4600in the browser and accept the security warning. - Start a local watcher with
yarn nx devwhenever you need live rebuilds across packages and the website. packages/ag-charts-website/src/content/gallery/data.jsonowns gallery example metadata.packages/ag-charts-website/src/content/docs-nav/nav.jsonowns docs navigation structure.- Docs map from
packages/ag-charts-website/src/content/docs/${pageName}/index.mdocto/charts/javascript/${pageName}/.
Build Watch Status Monitoring
The yarn nx dev watch script (external/ag-shared/scripts/watch/watch.js) maintains a status file at node_modules/.cache/ag-watch-status.json for monitoring build state.
Check this file to:
- Ensure no builds are in progress before starting operations (status !=
BUILDING) - Monitor build health via
recentBuildsarray andtargetHistorystats - Track build progress after file changes
Key fields:
status:STARTING|RUNNING|BUILDING|IDLE|STOPPEDcurrentBuild: Active build details (only whenBUILDING)recentBuilds: Last 10 builds with status/duration/errorstargetHistory: Per-target success/failure counts
Usage:
# Wait for idle before operations
while [ "$(jq -r '.status' node_modules/.cache/ag-watch-status.json 2>/dev/null)" = "BUILDING" ]; do
sleep 2
done
# Start watch if needed
node external/ag-shared/scripts/watch/watch.js charts &
Production URLs
- The production base URLs for the Astro site is https://www.ag-grid.com/
Staging URLs
- The staging base URLs for the Astro site is https://charts-staging.ag-grid.com/
- NOTE: That the
/chartspath prefix is not used for paths on the staging site.
- NOTE: That the
More from ag-grid/ag-charts
estimate-jira
Estimate complexity, effort, and risks for JIRA tickets, features, or projects. Generates structured reports with time estimates, dependencies, risk analysis, and known unknowns. Use when user asks to "estimate", "size", or "analyze complexity" of work items.
43pr-split
Split a branch into a logical sequence of stacked PRs for easier review
27batch-lint-cleanup
Analyze ESLint violations and auto-fix specific rules in isolation
23recall
Load branch context and browse project memory for session resumption
22plunker
Create and manage Plunker (plnkr.co) code examples for AG Charts and AG Grid. Use this skill whenever the user mentions plunker, plnkr, or plunk, wants to create a shareable code demo or bug reproduction, needs to fork or modify an existing plunk, or asks for a live code example they can share via URL. This includes creating repros for JIRA tickets, building demos for stakeholders, downloading plunks to inspect them, or making any interactive code example hosted on plnkr.co. Also trigger when users ask for "a shareable example", "a repro", "a demo I can send", or "a live example" — even without explicitly saying "plunker".
22sync-ag-shared
Sync ag-shared subrepo changes across ag-charts, ag-grid, and ag-studio repos
22