@blueprint-chart/editor
Static-site bundle of the Blueprint Chart editor. Use it self-hosted or via the live version at blueprintchart.com.
Live version
Self-host
Install the package and point any static file server at the dist/ directory.
npm install @blueprint-chart/editor
npx serve node_modules/@blueprint-chart/editor/dist
Or copy node_modules/@blueprint-chart/editor/dist/* into your own static hosting (S3, Nginx, GitHub Pages, etc.).
Develop
See the main repository for development instructions.
Optional: Accounts & hosted charts (Supabase)
The editor works fully without an account — charts live in your browser and embed via self-contained base64 links. To additionally let users sign in, store charts in the cloud, and publish live permalinks, configure Supabase.
1. Create a Supabase project and apply the schema
The schema lives in packages/editor/supabase/migrations/20260601000000_charts.sql
(creates the charts table and RLS policies — owner full access; public read of
published charts). Apply it with either method:
A. Supabase SQL Editor (no tooling). Open your project → SQL Editor → paste the file contents → Run. Always works.
B. Supabase CLI. This repo ships a ready packages/editor/supabase/ project, so
from that directory:
cd packages/editor
supabase link --project-ref YOUR-PROJECT-REF
supabase db push
db push only recognizes migrations named <timestamp>_name.sql and reads them
from the supabase/ project it's run against — hence cd packages/editor first.
If you keep your own supabase/ project elsewhere, copy
20260601000000_charts.sql into its supabase/migrations/ (keep the timestamped
name) before running supabase db push.
2. Configure credentials
Either bake them at build time:
VITE_SUPABASE_URL=https://YOUR-PROJECT.supabase.co
VITE_SUPABASE_ANON_KEY=YOUR-PUBLIC-ANON-KEY
…or deploy a runtime config.json next to index.html (overrides env, so one
build can be configured per deploy — see config.example.json):
{ "supabaseUrl": "https://YOUR-PROJECT.supabase.co", "supabaseAnonKey": "YOUR-PUBLIC-ANON-KEY" }
If neither is set (or only one value is present), the accounts feature stays off and the editor behaves exactly as the self-contained build.
3. Auth provider
Sign-in uses passwordless magic links. In your Supabase project enable the Email provider and add your deployed origin to the allowed redirect URLs.
License
MIT