40 Commits
Author SHA1 Message Date
Ninosaurier cbcb9a4572 Merge pull request 'fix(docs): resolve missing native Astro compiler bindings in root execution' (#24) from fix/#23-astro-compiler-pnpm-linux-binary into dev
CI / lint-and-format (push) Successful in 34s
CI / changeset-check (push) Successful in 31s
CI / unit-tests (push) Successful in 41s
CI / component-tests (push) Successful in 33s
Reviewed-on: #24

Merge pull request #24 from Ninosaurier/fix/#23-astro-compiler-pnpm-linux-binary

Fixes #23: Move optional Astro compiler bindings to root devDependencies to prevent pnpm v11 workspace purging and ensure deterministic binary downloads.
2026-08-16 07:28:45 +00:00
Ninosaurier 88991e353e fix(docs): resolve missing native Astro compiler bindings in root execution
CI / lint-and-format (push) Successful in 37s
CI / changeset-check (push) Successful in 27s
CI / unit-tests (push) Successful in 42s
CI / component-tests (push) Successful in 32s
CI / lint-and-format (pull_request) Successful in 35s
CI / changeset-check (pull_request) Successful in 25s
CI / unit-tests (pull_request) Successful in 37s
CI / component-tests (pull_request) Successful in 34s
pnpm v11 aggressively purges nested optional platform-specific dependencies during hoisted workspace resolution if the host detection mismatches local metadata. Moving these packages to root devDependencies bypasses pnpm's optional filtering logic, forcing a deterministic physical download of the required Rust compiler binary without cluttering the published library's package.json.

Fixes: #23
2026-08-15 21:33:53 +02:00
Ninosaurier 63dbbdb971 Merge pull request 'sync: merge main into dev' (#22) from main into dev
CI / lint-and-format (push) Successful in 34s
CI / changeset-check (push) Successful in 28s
CI / unit-tests (push) Successful in 39s
CI / component-tests (push) Successful in 29s
Reviewed-on: #22
2026-08-12 12:03:05 +00:00
Ninosaurier b480ecb268 Merge pull request 'docs(readme): remove outdated storybook root-script gap notice' (#21) from docs/fix-readme-storybook into main
CI / lint-and-format (push) Successful in 37s
CI / changeset-check (push) Successful in 27s
CI / unit-tests (push) Successful in 34s
CI / component-tests (push) Successful in 30s
CI / lint-and-format (pull_request) Successful in 33s
CI / changeset-check (pull_request) Successful in 28s
CI / unit-tests (pull_request) Successful in 39s
CI / component-tests (pull_request) Successful in 29s
Reviewed-on: #21
2026-08-12 11:52:15 +00:00
Ninosaurier 475a6cb634 docs(readme): remove outdated storybook root-script gap notice
CI / lint-and-format (push) Successful in 35s
CI / changeset-check (push) Successful in 27s
CI / unit-tests (push) Successful in 41s
CI / component-tests (push) Successful in 32s
CI / lint-and-format (pull_request) Successful in 35s
CI / changeset-check (pull_request) Successful in 31s
CI / unit-tests (pull_request) Successful in 37s
CI / component-tests (pull_request) Successful in 31s
Removes the note stating that running Storybook from the repository
root isn't set up yet, along with the old cd-into-package workaround
instructions. This gap was closed by the root-level pnpm run
storybook script added in #11, so the outdated guidance is no longer
accurate.
2026-08-12 13:47:01 +02:00
Ninosaurier f0c59a9b6f Merge pull request 'sync: merge dev into main' (#20) from dev into main
CI / lint-and-format (push) Successful in 38s
CI / changeset-check (push) Successful in 29s
CI / unit-tests (push) Successful in 37s
CI / component-tests (push) Successful in 29s
Reviewed-on: #20

Merge pull request #20 from dev into main

sync: merge dev into main

Syncs dev into main following the merge of PR #19 (storybook root
script).

Closes #11.
2026-08-12 11:22:40 +00:00
Ninosaurier 61ec0d839e Merge pull request 'build(scripts): add root-level pnpm run storybook script' (#19) from build/11-root-storybook-script into dev
CI / lint-and-format (push) Successful in 35s
CI / changeset-check (push) Successful in 32s
CI / unit-tests (push) Successful in 37s
CI / component-tests (push) Successful in 30s
CI / lint-and-format (pull_request) Successful in 36s
CI / changeset-check (pull_request) Successful in 28s
CI / unit-tests (pull_request) Successful in 38s
CI / component-tests (pull_request) Successful in 31s
Reviewed-on: #19

Adds a storybook script to the root package.json that filters into
the luna-charts package, so Storybook can be launched directly from
the repository root instead of requiring a manual cd into
packages/luna-charts. Updates README.md to document the new command
as part of the standard developer workflow.

Closes #11.
2026-08-12 10:48:59 +00:00
Ninosaurier 382536168b build(scripts): add root-level pnpm run storybook script
CI / lint-and-format (push) Successful in 34s
CI / changeset-check (push) Successful in 27s
CI / unit-tests (push) Successful in 41s
CI / component-tests (push) Successful in 30s
CI / lint-and-format (pull_request) Successful in 34s
CI / changeset-check (pull_request) Successful in 27s
CI / unit-tests (pull_request) Successful in 36s
CI / component-tests (pull_request) Successful in 30s
Adds a storybook script to the root package.json that filters into
the luna-charts package, so Storybook can be launched directly from
the repository root instead of requiring a manual cd into
packages/luna-charts. Updates README.md to document the new command
as part of the standard developer workflow.

 Closes #11.
2026-08-12 12:30:48 +02:00
Ninosaurier 956b2f277b Merge pull request 'chore(release): prepare v0.1.0 release for main' (#16) from dev into main
CI / lint-and-format (push) Successful in 34s
CI / changeset-check (push) Successful in 27s
CI / unit-tests (push) Successful in 34s
CI / component-tests (push) Successful in 30s
Reviewed-on: #16
2026-08-05 15:57:46 +00:00
Ninosaurier 37bb4e9ea2 Merge pull request 'chore(release): prepare v0.1.0 foundation release and update technology architecture' (#15) from update-technology-architecture into dev
CI / lint-and-format (push) Successful in 32s
CI / changeset-check (push) Successful in 31s
CI / unit-tests (push) Successful in 37s
CI / component-tests (push) Successful in 29s
CI / lint-and-format (pull_request) Successful in 33s
CI / changeset-check (pull_request) Successful in 24s
CI / unit-tests (pull_request) Successful in 39s
CI / component-tests (pull_request) Successful in 29s
Reviewed-on: #15

Merge pull request #15 from <branch-name>

chore(release): prepare v0.1.0 foundation release

Includes:
- Added Changeset for initial v0.1.0 release
- Updated README documentation
- Updated Technology Architecture documentation
- Updated ADR-0002
2026-08-05 15:52:19 +00:00
Ninosaurier 72c49e6b0f chore(changeset): prepare v0.1.0 release
CI / lint-and-format (push) Successful in 37s
CI / changeset-check (push) Successful in 25s
CI / unit-tests (push) Successful in 39s
CI / component-tests (push) Successful in 30s
CI / lint-and-format (pull_request) Successful in 32s
CI / changeset-check (pull_request) Successful in 28s
CI / unit-tests (pull_request) Successful in 36s
CI / component-tests (pull_request) Successful in 30s
2026-08-05 17:28:41 +02:00
Ninosaurier 9091bdcfae docs(update): update README to reflect .gitea/ CI setup and test image sourcing
CI / lint-and-format (push) Successful in 33s
CI / changeset-check (push) Successful in 26s
CI / unit-tests (push) Successful in 36s
CI / component-tests (push) Successful in 29s
Adds the .gitea/ directory to the project structure overview and
corrects the claim that local and CI test environments are identical.
Both are built from the same Dockerfile.test, but locally the image is
built on demand while CI pulls a prebuilt version — see ADR-0002 and
the Technology Architecture doc for details.
2026-08-05 17:20:41 +02:00
Ninosaurier 2ddf8961c2 docs(update): update README to reflect .gitea/ CI setup and test image sourcing
CI / lint-and-format (push) Successful in 34s
CI / changeset-check (push) Successful in 30s
CI / unit-tests (push) Successful in 37s
CI / component-tests (push) Successful in 30s
Adds the .gitea/ directory to the project structure overview and
corrects the claim that local and CI test environments are identical.
Both are built from the same Dockerfile.test, but locally the image is
built on demand while CI pulls a prebuilt version — see ADR-0002 and
the Technology Architecture doc for details.
2026-08-05 17:00:52 +02:00
Ninosaurier 7559a2725a Merge pull request 'ci(component-tests): add containerized component test workflow' (#14) from fix/ci-runner-test-component into dev
CI / lint-and-format (push) Successful in 39s
CI / changeset-check (push) Successful in 29s
CI / unit-tests (push) Successful in 42s
CI / component-tests (push) Successful in 32s
Merge branch 'fix/ci-runner-test-component' into 'dev'

ci(component-tests): add containerized component test workflow

Reviewed-on: #14
2026-08-04 12:34:04 +00:00
Ninosaurier caf0f3de2d ci(component-tests): add containerized component test workflow
CI / lint-and-format (push) Successful in 35s
CI / changeset-check (push) Successful in 28s
CI / unit-tests (push) Successful in 39s
CI / component-tests (push) Successful in 29s
CI / lint-and-format (pull_request) Successful in 36s
CI / changeset-check (pull_request) Successful in 33s
CI / unit-tests (pull_request) Successful in 37s
CI / component-tests (pull_request) Successful in 29s
Introduce dedicated CI container images and improve the component
test execution in Gitea Actions.

The workflow now uses reproducible runner environments, private
registry authentication and executes Playwright component tests
inside a prepared container.
2026-08-03 22:18:14 +02:00
Ninosaurier 856fea304a chore: scope workspace commands with pnpm filter
CI / lint-and-format (push) Successful in 36s
CI / changeset-check (push) Successful in 32s
CI / unit-tests (push) Successful in 38s
CI / component-tests (push) Failing after 28s
2026-08-02 15:39:19 +02:00
Ninosaurier 3b9a78bf9d style: format luna charts source 2026-08-02 15:38:45 +02:00
Ninosaurier 75d4632052 chore: update prettier configuration 2026-08-02 15:38:24 +02:00
Ninosaurier 9089a4ef60 fix(eslint): fix: allow stencil jsx helper in eslint
CI / changeset-check (push) Canceled after 0s
CI / unit-tests (push) Canceled after 0s
CI / component-tests (push) Canceled after 0s
CI / lint-and-format (push) Canceled after 4m4s
2026-08-02 15:26:15 +02:00
Ninosaurier 88154775de eslint(error): removed double line 2026-08-02 15:25:53 +02:00
Ninosaurier 5211b5f76a fix(ci): adjust root lint script to execute eslint directly within project directory 2026-08-02 15:25:31 +02:00
Ninosaurier b0ae34dbaa chore(lint): improve monorepo workspace scripts 2026-08-02 15:03:49 +02:00
Ninosaurier a92d83a5f4 fix(ci):
CI / lint-and-format (push) Failing after 34s
CI / changeset-check (push) Successful in 31s
CI / unit-tests (push) Successful in 42s
CI / component-tests (push) Failing after 25s
trigger workflow on all branch pushes and fix component tests setup
2026-08-02 14:35:50 +02:00
Ninosaurier 35747ec681 ci: trigger workflow on all branch pushes and fix component tests setup
- Changed push branch filter to wildcard '*' to test feature branches before merging
- Kept the missing pnpm/node setup fix for the component-tests job
2026-08-02 14:33:03 +02:00
Ninosaurier 6d1aeb6ee2 ci: trigger workflow on all branch pushes and fix component tests setup
- Changed push branch filter to wildcard '*' to test feature branches before merging
- Kept the missing pnpm/node setup fix for the component-tests job
2026-08-02 14:32:24 +02:00
Ninosaurier 768a43d9b6 fix(ci): add missing node and pnpm setup to component tests
Every job runs in an isolated container. The component-tests job
was missing the Node.js and pnpm installation steps, causing
command not found errors (exit code 127) during local execution.
2026-08-02 14:30:05 +02:00
Ninosaurier 75c8300d84 fix(runner): Fixed wrong label. the right label for using the runner is ubuntu-docker-dind
CI / lint-and-format (push) Failing after 1m31s
CI / changeset-check (push) Successful in 29s
CI / unit-tests (push) Successful in 39s
CI / component-tests (push) Failing after 5s
2026-08-02 14:14:12 +02:00
Ninosaurier 97f99a23ae fix-lint(lint-violation): Updated readme.md It had a lint-violation
CI / lint-and-format (push) Canceled after 0s
CI / changeset-check (push) Canceled after 0s
CI / unit-tests (push) Canceled after 0s
CI / component-tests (push) Canceled after 0s
2026-08-02 14:11:38 +02:00
Ninosaurier dd2874d8b0 feat(ci): add quality gate workflow for dev/main
CI / lint-and-format (push) Canceled after 0s
CI / changeset-check (push) Canceled after 0s
CI / unit-tests (push) Canceled after 0s
CI / component-tests (push) Canceled after 0s
Adds automated checks that were previously only run manually and
locally, closing the last remaining gap before dev can be merged
into main with confidence.

Runs on every push and pull request targeting dev or main:
- lint (eslint)
- format check (prettier --check)
- changeset presence check (non-blocking for now, see comment in
  workflow file)
- unit tests (vitest)
- component/browser tests (vitest + playwright, via the existing
  Docker test setup)

Fixes: #10
2026-08-02 02:00:57 +02:00
Ninosaurier 6e13c29141 chore(tooling): add prettier format check script 2026-08-02 01:44:40 +02:00
Ninosaurier 85b1ca240e fix(deps): pin playwright exactly and respect lockfile in docker build
The Playwright version was pinned with a caret range and the test
Dockerfile deleted pnpm-lock.yaml before installing, so every image
build silently re-resolved to the latest matching Playwright version.
This caused the npm package and the Docker base image to drift apart.

- packages/luna-charts/package.json: pin playwright to 1.62.1 exactly
- Dockerfile.test: stop deleting pnpm-lock.yaml before install, and
  use --frozen-lockfile so a mismatch between package.json and the
  lockfile fails the build loudly instead of resolving silently
2026-08-02 01:31:47 +02:00
Ninosaurier 82cfca4215 chore(luna-charts): update generated custom elements metadata 2026-08-02 01:12:57 +02:00
Ninosaurier c1a1e71240 docs(readme): update readme content 2026-08-02 01:00:25 +02:00
Ninosaurier 2b742e95f1 fix(lint): resolve all outstanding eslint errors 2026-08-02 00:52:27 +02:00
Ninosaurier a09d83fb53 fix(deps): pin playwright to 1.62.1 and sync docker test image
Playwright was previously pinned with a caret range (^1.61.1), which
allowed pnpm to silently resolve a newer minor version after the
lockfile was regenerated. This caused a version mismatch with the
Docker test image, which still referenced 1.61.1.

- packages/luna-charts/package.json: pin playwright to 1.62.1 exactly
- Dockerfile.test: bump base image to v1.62.1-noble to match
2026-08-02 00:45:30 +02:00
Ninosaurier 575f9202a8 docs(readme): add documentation and storybook start instructions
The README was missing instructions for running the documentation
site and Storybook locally, so contributors had to guess or dig
through package.json scripts to find them. Documents the existing
`pnpm run docs` command and the current Storybook workflow, including
the known limitation that it must be run from within
`packages/luna-charts` until a root-level filter script is set up.
2026-08-02 00:01:04 +02:00
Ninosaurier bb6009d26c build(workspace):
add root command for documentation development

Expose the Astro documentation development server through the root
workspace to simplify the local development workflow. Developers can
now start the documentation site without changing into the docs directory.

Fixes: #12
2026-08-01 23:41:47 +02:00
Ninosaurier 568bc3a98b textdocs(readme):
add repository mirror and issue tracking notice

To prevent fragmentation of feedback, we want all bug reports and
contributions to be centralized on our main self-hosted platform.
GitHub lacks active monitoring for issues, so users need clear
direction on where to officially open them.
2026-08-01 23:12:45 +02:00
Ninosaurier 3dc61e5087 build: fix missing native linux bindings for oxc and rolldown
Explicitly added @oxc-parser/binding-linux-x64-gnu and @rolldown/binding-linux-x64-gnu as devDependencies. This bypasses issues where pnpm occasionally skips optional native platform bindings during installation, which previously caused CriticalPresetLoadError when loading StencilJS plugins.
2026-07-22 23:50:31 +02:00
Ninosaurier 2991ddf567 Update(docs): add project README and CONTRIBUTING guide
Adds a proper project README (description, tech stack, structure,
setup, scripts) and a CONTRIBUTING guide (governance summary,
workflow, PR expectations), both previously missing or placeholder-only.
2026-07-18 09:38:43 +02:00
30 changed files with 4885 additions and 5099 deletions
+5
View File
@@ -0,0 +1,5 @@
---
'luna-charts': minor
---
Establish the initial project foundation with architecture, documentation, governance, and development tooling.
+18
View File
@@ -0,0 +1,18 @@
FROM node:22-bullseye
# Install Docker CLI + Compose V2 plugin from Docker's official apt repo
# (Debian's own docker.io package ships an outdated Docker version and
# does not include the compose plugin at all).
RUN apt-get update \
&& apt-get install -y ca-certificates curl gnupg \
&& install -m 0755 -d /etc/apt/keyrings \
&& curl -fsSL https://download.docker.com/linux/debian/gpg -o /etc/apt/keyrings/docker.asc \
&& chmod a+r /etc/apt/keyrings/docker.asc \
&& echo \
"deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/debian bullseye stable" \
| tee /etc/apt/sources.list.d/docker.list > /dev/null \
&& apt-get update \
&& apt-get install -y docker-ce-cli docker-compose-plugin \
&& rm -rf /var/lib/apt/lists/*
RUN corepack enable
+90
View File
@@ -0,0 +1,90 @@
name: CI
on:
push:
branches:
- '**'
pull_request:
branches: [dev, main]
jobs:
lint-and-format:
runs-on: ubuntu-docker-dind
container:
image: git.byting-pandas.ninja/ci/node22-docker:latest
credentials:
username: ${{ secrets.REGISTRY_USER }}
password: ${{ secrets.REGISTRY_TOKEN }}
steps:
- uses: actions/checkout@v4
- run: corepack enable
- run: corepack prepare pnpm@11.11.0 --activate
- run: pnpm install --frozen-lockfile
- name: Lint
run: pnpm lint
- name: Check formatting
run: pnpm format:check
changeset-check:
runs-on: ubuntu-docker-dind
container:
image: git.byting-pandas.ninja/ci/node22-docker:latest
credentials:
username: ${{ secrets.REGISTRY_USER }}
password: ${{ secrets.REGISTRY_TOKEN }}
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0
- run: corepack enable
- run: corepack prepare pnpm@11.11.0 --activate
- run: pnpm install --frozen-lockfile
- name: Verify changeset exists
continue-on-error: true
run: pnpm changeset status --since=origin/dev
unit-tests:
runs-on: ubuntu-docker-dind
container:
image: git.byting-pandas.ninja/ci/node22-docker:latest
credentials:
username: ${{ secrets.REGISTRY_USER }}
password: ${{ secrets.REGISTRY_TOKEN }}
steps:
- uses: actions/checkout@v4
- run: corepack enable
- run: corepack prepare pnpm@11.11.0 --activate
- run: pnpm install --frozen-lockfile
- name: Run unit tests
run: pnpm test:unit
component-tests:
runs-on: ubuntu-docker-dind
container:
image: git.byting-pandas.ninja/ci/luna-charts-test:v1.62.1
credentials:
username: ${{ secrets.REGISTRY_USER }}
password: ${{ secrets.REGISTRY_TOKEN }}
steps:
- uses: actions/checkout@v4
- run: corepack enable
- run: corepack prepare pnpm@11.11.0 --activate
- run: pnpm install --frozen-lockfile
- name: Run component tests (Playwright)
working-directory: packages/luna-charts
run: pnpm test:browser
+2 -1
View File
@@ -2,5 +2,6 @@
"singleQuote": true,
"semi": true,
"trailingComma": "es5",
"printWidth": 100
"printWidth": 100,
"bracketSameLine": true
}
+78
View File
@@ -0,0 +1,78 @@
# Contributing to LUNA Charts
Thank you for considering a contribution to LUNA Charts! This document explains how the project is governed, what's expected of a contribution, and how to get your change through review.
Before contributing, please also read our [Code of Conduct](./.github/CODE_OF_CONDUCT.md).
## Project Status
LUNA Charts is currently in its **groundwork phase** — foundational architecture, tooling, and testing infrastructure are being established before chart components are built out. Check the [Roadmap](./docs/src/content/docs/getting-started/roadmap.mdx) to see what's currently in scope.
## How the Project Is Governed
LUNA Charts balances open community contribution with a documented architecture. In short:
- **The architecture is the authoritative source for implementation decisions** — it's documented under [`docs/.../architecture/adm`](./docs/src/content/docs/architecture/adm) (Architecture Development Method) and [`docs/.../architecture/adr`](./docs/src/content/docs/architecture/adr) (Architecture Decision Records)
- **Contributions are reviewed on three levels**: automated checks (types, linting, tests, accessibility), architectural compliance (does it fit the documented architecture?), and general project quality (readability, maintainability, documentation)
- **A Pull Request can be rejected even if all automated checks pass** — for example, if it introduces an unnecessary public API change, bypasses accessibility mechanisms, or conflicts with a documented architectural decision
- Community members can propose architectural changes, but such changes only become official once the relevant ADR/ADM documentation has been updated to reflect them (see [Architecture Change Management](./docs/src/content/docs/architecture/adm/architecture-change-management.mdx))
If you're planning a larger change, especially one that touches the public API, rendering approach, or accessibility behavior, please open an issue or discussion first so it can be reviewed against the architecture before you invest time in an implementation.
## Getting Started
1. Fork the repository and clone your fork
2. Install dependencies:
```bash
pnpm install
```
3. Requirements: Node.js `>= 22.0.0`, pnpm `11.11.0` (via Corepack), and Docker (for component/browser tests)
## Making a Change
1. Create a branch from `main` with a descriptive name (e.g. `fix/axis-label-overflow`, `docs/update-technology-architecture`)
2. Make your change
3. Run the checks locally before opening a PR:
```bash
pnpm lint
pnpm test:unit
pnpm test:component # runs inside a Docker/Playwright container
pnpm test # runs both of the above
```
4. If your change affects published package behavior (bug fix, feature, breaking change), add a changeset:
```bash
pnpm changeset
```
Documentation-only or internal tooling changes generally don't need a changeset — if you're unsure, mention it in your PR description and a maintainer will advise.
## Pull Request Guidelines
- Keep PRs focused on a single concern where possible — smaller PRs are easier to review against the architecture
- Describe **what** changed and **why**, not just what the diff shows
- If your change affects accessibility behavior, explain how it was verified (e.g. which axe-core checks or manual screen-reader testing was done)
- If your change touches an area covered by an existing ADR, reference it and note whether the ADR needs a corresponding update
- Automated testing (unit, accessibility, linting) must pass before a PR can be merged
## Documentation Changes
Documentation lives in `docs/` (Starlight) and is a first-class contribution — fixing unclear wording, expanding examples, or correcting an outdated ADR/ADM page is just as valuable as a code change.
If your code change makes a documented architectural statement incorrect (for example, changing a technology choice or the repository structure), please update the relevant ADR/ADM page in the same PR, including a short **Change Log** entry at the end of that document explaining what changed and why. Keeping documentation in sync with implementation is part of the review criteria described above.
## Reporting Bugs and Suggesting Features
Please open an issue with:
- A clear description of the problem or suggestion
- Steps to reproduce (for bugs), including browser/OS if relevant to rendering or accessibility
- What you expected to happen vs. what actually happened
## Questions
If anything here is unclear, feel free to open a discussion or issue — improving this guide based on real contributor questions is welcome too.
+2 -4
View File
@@ -1,4 +1,4 @@
FROM mcr.microsoft.com/playwright:v1.61.1-noble
FROM mcr.microsoft.com/playwright:v1.62.1-noble
RUN corepack enable && corepack prepare pnpm@10 --activate
@@ -10,11 +10,9 @@ COPY . .
RUN rm -rf node_modules packages/**/node_modules
RUN rm -f pnpm-lock.yaml
ENV PNPM_CONFIG_SUPPORTED_ARCHITECTURES="current,linux-x64-gnu"
RUN pnpm install
RUN pnpm install --frozen-lockfile
WORKDIR /app/packages/luna-charts
+104 -1
View File
@@ -1,3 +1,106 @@
# LUNA-Charts
# LUNA Charts
LUNA Charts is a reusable, developer-friendly charting library designed to make accessible, WCAG-oriented data visualization the default rather than an afterthought.
> **Project status:** Groundwork phase. Core architecture and tooling are in place; production-ready chart components (starting with `BarChart`) are still in development. See the [Roadmap](./docs/src/content/docs/getting-started/roadmap.mdx) for details.
## Preface & Repository Mirror Notice
Please be aware of our repository structure:
* **Official Repository:** [git.byting-pandas.ninja/Ninosaurier/LUNA-Charts](https://git.byting-pandas.ninja/Ninosaurier/LUNA-Charts)
**Important:** All development, including issue tracking and contribution management, takes place exclusively on our self-hosted server. Issues and pull requests cannot be created or processed on this GitHub mirror. Please visit the original link above to report bugs or request features.
## Why LUNA Charts
Most charting libraries treat accessibility as an add-on. LUNA Charts builds it in from the start:
* **Accessible by default** — components are designed and tested against WCAG guidance from day one, not patched in afterward
* **Framework-agnostic** — built as standard Web Components (Stencil), usable in React, Vue, Angular, Svelte, or plain HTML
* **SVG-based rendering** — inspectable, stylable, and screen-reader-friendly output instead of an opaque canvas
## Tech Stack
| Area | Technology |
| --- | --- |
| Component framework | [Stencil](https://stenciljs.com) (compiles to standard Web Components) |
| Language | TypeScript |
| Package manager | pnpm (monorepo workspaces) |
| Unit & component testing | [Vitest](https://vitest.dev), with [Playwright](https://playwright.dev) as the browser provider |
| Accessibility testing | axe-core |
| Documentation | [Starlight](https://starlight.astro.build) |
| Component explorer | Storybook |
| Linting & formatting | ESLint, Prettier |
| Release management | [Changesets](https://github.com/changesets/changesets) |
The full set of architecture decisions behind these choices is documented in [`docs/.../architecture/adr`](./docs/src/content/docs/architecture/adr) and the broader [Architecture Development Method (ADM) documentation](./docs/src/content/docs/architecture/adm).
## Project Structure
```text
luna-charts/
├── packages/
│ └── luna-charts/ # The library itself (Stencil components, Storybook)
├── docs/ # Architecture docs, ADRs, guides (Starlight)
├── examples/ # Usage examples (framework integrations)
├── .changeset/ # Release/versioning configuration
├── .github/ # Community health files (Code of Conduct, etc.)
└── .gitea/ # CI workflows (Gitea Actions) and CI runner image
```
## Getting Started
### Prerequisites
* Node.js `>= 22.0.0`
* pnpm `11.11.0` (see `devEngines` in `package.json`; pnpm will be downloaded automatically via Corepack if missing)
* Docker (required for running component/browser tests locally, see below)
### Installation
```bash
git clone https://github.com/Ninosaurier/LUNA-Charts.git
cd luna-charts
pnpm install
```
or
```bash
git clone https://git.byting-pandas.ninja/Ninosaurier/LUNA-Charts.git
cd luna-charts
pnpm install
```
### Common commands
| Command | Description |
| --- | --- |
| `pnpm test:unit` | Run unit tests for the `luna-charts` package |
| `pnpm test:component` | Run component/browser tests inside the containerized Playwright environment |
| `pnpm test` | Run the full test suite (unit + component) |
| `pnpm changeset` | Record a changeset for your change (required for any user-facing change) |
| `pnpm run docs` | Start the documentation site locally (astroJS) |
| `pnpm run lint` | Run the linter to check for code style and quality issues |
| `pnpm run format` | Run the formatter to automatically fix code style issues |
| `pnpm run test:browser` | Run browser tests (only works inside the `packages/luna-charts` directory) |
| `pnpm run storybook` | Start the storybook documentation |
Component and browser tests run inside Docker (`docker-compose.test.yaml`), based on the same `Dockerfile.test` used to build the image CI tests against, to guarantee a reproducible browser environment — you don't need Playwright browsers installed locally. Locally this image is built on demand; in CI a prebuilt version of the same image is pulled directly (see [ADR-0002](./docs/src/content/docs/architecture/adr/000200-technology-stack.mdx) and the [Technology Architecture](./docs/src/content/docs/architecture/adm/technology-architecture.mdx#66-test-execution-environment) doc for details).
## Documentation
* **Architecture documentation**: see `docs/` — includes the full Architecture Development Method (ADM) documentation (vision, business architecture, technology architecture, governance, migration planning) and all Architecture Decision Records (ADRs)
* **Contributing**: see [CONTRIBUTING.md](./CONTRIBUTING.md)
* **Code of Conduct**: see [.github/CODE_OF_CONDUCT.md](./.github/CODE_OF_CONDUCT.md)
## License
LUNA Charts is licensed under the [GNU Lesser General Public License v3.0 (LGPL-3.0)](./LICENSE).
-4323
View File
File diff suppressed because it is too large Load Diff
@@ -150,19 +150,39 @@ LUNA Charts follows a multi-layer quality assurance model.
### 6.6 Test Execution Environment
Component and browser tests (Vitest browser mode, see ADR-0002) run inside a **containerized Playwright environment** rather than directly on contributor or CI host machines.
Component and browser tests (Vitest browser mode, see ADR-0002) run inside
a **containerized Playwright environment** rather than directly on
contributor or CI host machines.
#### Characteristics
- A dedicated `Dockerfile.test`, based on the official Playwright container image, provides a reproducible browser environment with pinned browser versions
- `docker-compose.test.yaml` orchestrates the test execution, isolating dependencies from the host system
- The same containerized environment is used locally by contributors and in Continuous Integration, avoiding "works on my machine" discrepancies caused by differing local Playwright/browser installations
- A dedicated `Dockerfile.test`, based on the official Playwright container
image, provides a reproducible browser environment with pinned browser
versions
- Locally, `docker-compose.test.yaml` builds this image from source and
orchestrates test execution, isolating dependencies from the host system
- In Continuous Integration, the same `Dockerfile.test` is built and
pushed to the project's container registry out-of-band (tagged by
Playwright version, e.g. `luna-charts-test:v1.62.1`); CI jobs pull this
prebuilt image directly rather than rebuilding it on every run, then
check out the current commit and install dependencies inside the running
container before executing tests
- `Dockerfile.test` remains the single source of truth for the test
environment definition in both cases — only *when* the image is built
(on demand locally, ahead of time for CI) differs
#### Rationale
- Ensures deterministic, reproducible accessibility and browser test results independent of the host operating system
- Removes the need for contributors to install and maintain matching Playwright browser binaries locally
- Aligns automated testing (Section 6.16.4) with a single, version-controlled execution environment
- Ensures deterministic, reproducible accessibility and browser test
results independent of the host operating system
- Removes the need for contributors to install and maintain matching
Playwright browser binaries locally
- Avoids rebuilding the Playwright/browser image on every CI run, which
would otherwise require Docker-in-Docker access inside the CI runner —
significant infrastructure complexity for a single-service image build
- Aligns automated testing (Section 6.16.4) with a single,
version-controlled execution environment definition, even though the
build trigger differs between local development and CI
## 7. Release & Distribution Model
@@ -256,3 +276,31 @@ Component and browser tests are executed inside a Docker-based Playwright enviro
**Impact**
This clarifies an already-implemented part of the testing strategy (Section 6) and does not change any other architectural decision in this document.
### 2026-08-04 CI uses a prebuilt test image instead of rebuilding per run
**Reason**
The initial implementation of Section 6.6 assumed CI would build
`Dockerfile.test` fresh on every run, identical to local execution. In
practice, this required Docker-in-Docker access inside the CI runner
purely to build a single-service image — disproportionate operational
complexity (privileged sidecar container, custom pod networking,
runner-level configuration) for the orchestration value actually needed,
since `docker-compose.test.yaml` defines only one service with no
inter-service dependencies.
**Changes**
- Section 6.6 updated to describe the actual CI flow: `Dockerfile.test` is
built and pushed to the registry out-of-band (not on every CI run), and
CI jobs pull the prebuilt image, then check out the current commit and
install dependencies at runtime
- Clarified that `Dockerfile.test` remains the single source of truth for
the test environment definition; only the build trigger differs between
local and CI usage
**Impact**
No other architectural decision in this document is affected. Local
component testing (`pnpm test:component`) is unchanged.
@@ -236,3 +236,89 @@ During implementation, Jest was replaced with Vitest as the unit testing tool. S
**Impact**
Playwright remains part of the technology stack, but its architectural role changes from an independent browser test runner to the browser engine used by Vitest. No other decisions in this ADR are affected.
### 2026-08-03 Continuous Integration: GitHub Actions replaced with Gitea Actions
**Reason**
During implementation, the project moved to a self-hosted Gitea instance
with Gitea Actions (`act_runner`) instead of GitHub Actions. The ADR's
"Considered Alternatives" and "Decision" tables still listed GitHub
Actions, which no longer matched the actual CI/CD tooling in use.
**Changes**
- "Considered Alternatives" table: `Continuous Integration` row updated —
considered alternatives changed to *GitHub Actions, GitLab CI, Azure
Pipelines, Gitea Actions*; selected technology changed to **Gitea
Actions**
- "Decision" table: **GitHub Actions** entry replaced with **Gitea
Actions**
- "Rationale" section: `GitHub Actions` subsection replaced with `Gitea
Actions`, noting that workflows run on a self-hosted `act_runner`
(Docker-in-Docker mode) against the project's own Gitea instance
**Impact**
Only the Continuous Integration technology choice is affected. Workflow
syntax remains GitHub-Actions-compatible (Gitea Actions is designed to be
largely compatible with the GitHub Actions workflow format), so no other
architectural decisions in this ADR are impacted.
### 2026-08-04 Component test CI execution: prebuilt image instead of Docker-in-Docker
**Reason**
Component tests run inside a container built from `Dockerfile.test`
(based on the official Playwright image). Running this build step inside
every CI job would require Docker-in-Docker (DinD) access on the
self-hosted Gitea Actions runner — a privileged sidecar container, custom
pod networking, and runner-level configuration — solely to build a
single-service image with no inter-service orchestration need.
**Considered Alternatives**
| Alternative | Description |
| ----------- | ----------- |
| Build `Dockerfile.test` fresh on every CI run (DinD) | Mirrors the local `docker compose up --build` flow exactly inside a DinD-enabled CI job. |
| Replicate `Dockerfile.test`'s steps directly as CI workflow steps, using the public Playwright image | Avoids Docker entirely in CI, but duplicates the test environment definition in two places (`Dockerfile.test` and the workflow YAML), risking drift between local and CI environments. |
| **Build and push `Dockerfile.test` out-of-band, pull the prebuilt image in CI (selected)** | `Dockerfile.test` remains the only definition of the test environment; the resulting image is built and pushed to the registry separately (tagged by Playwright version), and CI jobs simply pull it and run tests — no Docker access needed at test time. |
Building fresh on every run was rejected due to the disproportionate DinD
infrastructure complexity for a single-service build. Replicating the
steps in the workflow file was rejected because it reintroduces a second,
manually-synchronized source of truth for the test environment.
**Decision**
`Dockerfile.test` is built and pushed to the project's container registry
out-of-band (not as part of the CI pipeline), tagged by Playwright
version (e.g. `luna-charts-test:v1.62.1`). The `component-tests` CI job
pulls this prebuilt image directly, checks out the current commit, and
runs the test command — no Docker access is required inside the CI job
container.
**Consequences**
*Positive*
- `Dockerfile.test` remains the single source of truth for the test
environment definition
- No Docker-in-Docker, privileged containers, or custom pod networking
required in the CI job itself
- Faster, simpler `component-tests` job
*Negative*
- The test image must be rebuilt and pushed manually (or via a separate,
intentionally-triggered process) whenever `Dockerfile.test` changes;
forgetting this step means CI runs against a stale image
- This is considered an acceptable trade-off given how infrequently
`Dockerfile.test` changes, versus the ongoing operational cost of
maintaining DinD access in the runner
**Impact**
Local component testing (`pnpm test:component` via Docker Compose) is
unaffected — it continues to build `Dockerfile.test` fresh via
`docker-compose.test.yaml`. Only the CI-side image sourcing changes.
+30 -4
View File
@@ -1,8 +1,34 @@
// For more info, see https://github.com/storybookjs/eslint-plugin-storybook#configuration-flat-config-format
import storybook from "eslint-plugin-storybook";
import js from "@eslint/js";
import tseslint from "typescript-eslint";
import js from '@eslint/js';
export default [
{
ignores: [
"**/dist/**",
"**/www/**",
"**/node_modules/**",
"**/.stencil/**",
"**/loader/**",
],
},
export default [js.configs.recommended, {
ignores: ['**/dist/**', '**/www/**', '**/node_modules/**', '**/.stencil/**'],
}, ...storybook.configs["flat/recommended"]];
js.configs.recommended,
...tseslint.configs.recommended,
...storybook.configs["flat/recommended"],
{
files: ["**/*.tsx"],
rules: {
"@typescript-eslint/no-unused-vars": [
"error",
{
varsIgnorePattern: "^h$",
},
],
},
},
];
+13 -2
View File
@@ -4,11 +4,14 @@
"description": "",
"main": "index.js",
"scripts": {
"lint": "eslint .",
"docs": "pnpm --filter docs run dev",
"lint": "pnpm --filter luna-charts run lint",
"format": "prettier --write .",
"format:check": "pnpm --filter luna-charts run format:check",
"changeset": "changeset",
"version": "changeset version",
"release": "changeset publish",
"storybook": "pnpm --filter luna-charts run storybook",
"test:unit": "pnpm --filter luna-charts test:unit",
"test:component": "docker compose -f docker-compose.test.yaml up --build --abort-on-container-exit --exit-code-from test",
"test": "pnpm test:unit && pnpm test:component"
@@ -30,7 +33,15 @@
"type": "module",
"devDependencies": {
"@changesets/cli": "^2.31.0",
"@eslint/js": "^10.0.1",
"eslint": "^10.6.0",
"prettier": "^3.9.4"
"eslint-config-prettier": "^10.1.8",
"eslint-plugin-storybook": "10.5.0",
"prettier": "^3.9.4",
"typescript-eslint": "^8.65.0",
"@astrojs/compiler-binding-linux-x64-gnu": "0.3.2",
"@astrojs/compiler-binding-win32-x64-msvc": "0.3.2",
"@astrojs/compiler-binding-darwin-x64": "0.3.2",
"@astrojs/compiler-binding-darwin-arm64": "0.3.2"
}
}
+3 -4
View File
@@ -1,4 +1,3 @@
/**
* This is an autogenerated file created by the Stencil compiler.
* DO NOT MODIFY IT MANUALLY
@@ -29,7 +28,7 @@ interface ComponentCompilerTypeReference {
* - globally
* - by importing it into a file (and is defined elsewhere)
*/
location: "local" | "global" | "import";
location: 'local' | 'global' | 'import';
/**
* The path to the type reference, if applicable (global types should not need a path associated with them)
*/
@@ -152,7 +151,7 @@ export interface JsonDocsComponent {
/**
* The encapsulation strategy for a component
*/
encapsulation: "shadow" | "scoped" | "none";
encapsulation: 'shadow' | 'scoped' | 'none';
/**
* The tag name for the component, for use in HTML
*/
@@ -467,7 +466,7 @@ export interface StyleDoc {
* Used to inform Stencil where the start of a new property's description starts (and where the previous description
* ends).
*/
annotation: "prop";
annotation: 'prop';
/**
* The Stencil style-mode that is associated with this property.
*/
+16 -7
View File
@@ -1,5 +1,5 @@
{
"timestamp": "2026-07-12T12:51:52",
"timestamp": "2026-08-01T23:02:04",
"compiler": {
"name": "@stencil/core",
"version": "4.43.5",
@@ -17,10 +17,10 @@
"props": [
{
"name": "first",
"type": "string",
"type": "string | undefined",
"complexType": {
"original": "string",
"resolved": "string",
"resolved": "string | undefined",
"references": {}
},
"mutable": false,
@@ -31,6 +31,9 @@
"values": [
{
"type": "string"
},
{
"type": "undefined"
}
],
"optional": true,
@@ -40,10 +43,10 @@
},
{
"name": "last",
"type": "string",
"type": "string | undefined",
"complexType": {
"original": "string",
"resolved": "string",
"resolved": "string | undefined",
"references": {}
},
"mutable": false,
@@ -54,6 +57,9 @@
"values": [
{
"type": "string"
},
{
"type": "undefined"
}
],
"optional": true,
@@ -63,10 +69,10 @@
},
{
"name": "middle",
"type": "string",
"type": "string | undefined",
"complexType": {
"original": "string",
"resolved": "string",
"resolved": "string | undefined",
"references": {}
},
"mutable": false,
@@ -77,6 +83,9 @@
"values": [
{
"type": "string"
},
{
"type": "undefined"
}
],
"optional": true,
+6 -1
View File
@@ -32,6 +32,9 @@
"loader/"
],
"scripts": {
"lint": "eslint .",
"format:check": "prettier --check .",
"format": "prettier --write .",
"build": "stencil build",
"start": "stencil build --dev --watch --serve",
"test": "stencil-test --prod",
@@ -42,6 +45,8 @@
"storybook": "storybook dev -p 6006 --no-open"
},
"devDependencies": {
"@oxc-parser/binding-linux-x64-gnu": "^0.141.0",
"@rolldown/binding-linux-x64-gnu": "^1.2.0",
"@stencil/core": "^4.43.5",
"@stencil/storybook-plugin": "^0.7.0",
"@stencil/vitest": "^1.8.3",
@@ -51,7 +56,7 @@
"@vitest/browser-playwright": "^4.0.0",
"axe-core": "^4.12.1",
"eslint-plugin-storybook": "10.5.0",
"playwright": "^1.61.1",
"playwright": "^1.62.1",
"storybook": "^10.5.0",
"vitest": "^4.0.0"
},
+1 -5
View File
@@ -95,11 +95,7 @@ function App() {
return (
<>
<div>
<my-component
first="Stencil"
middle="'Don't call me a framework'"
last="JS"
></my-component>
<my-component first="Stencil" middle="'Don't call me a framework'" last="JS"></my-component>
</div>
</>
);
+52 -52
View File
@@ -1,68 +1,68 @@
/* eslint-disable */
/* tslint:disable */
/**
* This is an autogenerated file created by the Stencil compiler.
* It contains typing information for all components that exist in this project.
*/
import { HTMLStencilElement, JSXBase } from "@stencil/core/internal";
import { HTMLStencilElement, JSXBase } from '@stencil/core/internal';
export namespace Components {
interface MyComponent {
/**
* The first name
*/
"first"?: string;
/**
* The last name
*/
"last"?: string;
/**
* The middle name
*/
"middle"?: string;
}
interface MyComponent {
/**
* The first name
*/
first?: string;
/**
* The last name
*/
last?: string;
/**
* The middle name
*/
middle?: string;
}
}
declare global {
interface HTMLMyComponentElement extends Components.MyComponent, HTMLStencilElement {
}
var HTMLMyComponentElement: {
prototype: HTMLMyComponentElement;
new (): HTMLMyComponentElement;
};
interface HTMLElementTagNameMap {
"my-component": HTMLMyComponentElement;
}
interface HTMLMyComponentElement extends Components.MyComponent, HTMLStencilElement {}
var HTMLMyComponentElement: {
prototype: HTMLMyComponentElement;
new (): HTMLMyComponentElement;
};
interface HTMLElementTagNameMap {
'my-component': HTMLMyComponentElement;
}
}
declare namespace LocalJSX {
interface MyComponent {
/**
* The first name
*/
"first"?: string;
/**
* The last name
*/
"last"?: string;
/**
* The middle name
*/
"middle"?: string;
}
interface MyComponent {
/**
* The first name
*/
first?: string;
/**
* The last name
*/
last?: string;
/**
* The middle name
*/
middle?: string;
}
interface MyComponentAttributes {
"first": string;
"middle": string;
"last": string;
}
interface MyComponentAttributes {
first: string;
middle: string;
last: string;
}
interface IntrinsicElements {
"my-component": Omit<MyComponent, keyof MyComponentAttributes> & { [K in keyof MyComponent & keyof MyComponentAttributes]?: MyComponent[K] } & { [K in keyof MyComponent & keyof MyComponentAttributes as `attr:${K}`]?: MyComponentAttributes[K] } & { [K in keyof MyComponent & keyof MyComponentAttributes as `prop:${K}`]?: MyComponent[K] };
}
interface IntrinsicElements {
'my-component': Omit<MyComponent, keyof MyComponentAttributes> & { [K in keyof MyComponent & keyof MyComponentAttributes]?: MyComponent[K] } & {
[K in keyof MyComponent & keyof MyComponentAttributes as `attr:${K}`]?: MyComponentAttributes[K];
} & { [K in keyof MyComponent & keyof MyComponentAttributes as `prop:${K}`]?: MyComponent[K] };
}
}
export { LocalJSX as JSX };
declare module "@stencil/core" {
export namespace JSX {
interface IntrinsicElements {
"my-component": LocalJSX.IntrinsicElements["my-component"] & JSXBase.HTMLAttributes<HTMLMyComponentElement>;
}
declare module '@stencil/core' {
export namespace JSX {
interface IntrinsicElements {
'my-component': LocalJSX.IntrinsicElements['my-component'] & JSXBase.HTMLAttributes<HTMLMyComponentElement>;
}
}
}
@@ -26,7 +26,7 @@ export const Primary: Story = {
last: 'Doe',
middle: 'Michael',
},
render: (props) => <my-component {...props} />,
render: props => <my-component {...props} />,
};
/**
@@ -1,19 +1,15 @@
# my-component
<!-- Auto Generated Below -->
## Properties
| Property | Attribute | Description | Type | Default |
| -------- | --------- | --------------- | -------- | ----------- |
| `first` | `first` | The first name | `string` | `undefined` |
| `last` | `last` | The last name | `string` | `undefined` |
| `middle` | `middle` | The middle name | `string` | `undefined` |
| Property | Attribute | Description | Type | Default |
| -------- | --------- | --------------- | --------------------- | ----------- |
| `first` | `first` | The first name | `string \| undefined` | `undefined` |
| `last` | `last` | The last name | `string \| undefined` | `undefined` |
| `middle` | `middle` | The middle name | `string \| undefined` | `undefined` |
---
----------------------------------------------
*Built with [StencilJS](https://stenciljs.com/)*
_Built with [StencilJS](https://stenciljs.com/)_
+1 -1
View File
@@ -1,4 +1,4 @@
<!DOCTYPE html>
<!doctype html>
<html dir="ltr" lang="en">
<head>
<meta charset="utf-8" />
@@ -9,12 +9,12 @@ export const axeCoreChecker: A11yChecker = {
return {
checkerName: 'axe-core',
violations: results.violations.map((violations) => ({
violations: results.violations.map(violations => ({
id: violations.id,
impact: violations.impact ?? null,
description: violations.help,
helpUrl: violations.helpUrl,
nodes: violations.nodes.map((node) => node.target.join(' ')),
nodes: violations.nodes.map(node => node.target.join(' ')),
})),
};
},
@@ -1,12 +1,10 @@
import type { A11yChecker, A11yCheckResult } from './checkers/types';
import { axeCoreChecker } from './checkers/axe-core.checker';
const a11yCheckerRegistry: A11yChecker[] = [
axeCoreChecker,
];
const a11yCheckerRegistry: A11yChecker[] = [axeCoreChecker];
export async function runA11yChecks(rootElement: Element): Promise<A11yCheckResult[]> {
return Promise.all(a11yCheckerRegistry.map((a11yChecker) => a11yChecker.run(rootElement)));
return Promise.all(a11yCheckerRegistry.map(a11yChecker => a11yChecker.run(rootElement)));
}
export type { A11yChecker, A11yCheckResult, A11yViolation } from './checkers/types';
@@ -3,7 +3,7 @@ import type { A11yCheckResult } from './checkers/types';
expect.extend({
toHaveNoA11yViolations(results: A11yCheckResult[]) {
const failing = results.filter((results) => results.violations.length > 0);
const failing = results.filter(results => results.violations.length > 0);
if (failing.length === 0) {
return {
@@ -14,11 +14,9 @@ expect.extend({
const message = failing
.map(
(results) =>
results =>
`[${results.checkerName}] ${results.violations.length} violation(s):\n` +
results.violations
.map((validation) => ` - ${validation.id} (${validation.impact}): ${validation.description}\n affected: ${validation.nodes.join(', ')}`)
.join('\n')
results.violations.map(validation => ` - ${validation.id} (${validation.impact}): ${validation.description}\n affected: ${validation.nodes.join(', ')}`).join('\n'),
)
.join('\n\n');
+4 -13
View File
@@ -5,10 +5,7 @@
"allowUnreachableCode": false,
"declaration": false,
"experimentalDecorators": true,
"lib": [
"dom",
"es2022"
],
"lib": ["dom", "es2022"],
"moduleResolution": "bundler",
"module": "esnext",
"target": "es2022",
@@ -18,14 +15,8 @@
"jsx": "react",
"jsxFactory": "h",
"jsxFragmentFactory": "h.Fragment",
"types": [
"@stencil/vitest/globals"
]
"types": ["@stencil/vitest/globals"]
},
"include": [
"src"
],
"exclude": [
"node_modules"
]
"include": ["src"],
"exclude": ["node_modules"]
}
+1 -1
View File
@@ -1,4 +1,4 @@
import { defineCustomElements } from "./loader";
import { defineCustomElements } from './loader';
import './src/testing/a11y/matchers';
defineCustomElements();
+4283 -627
View File
File diff suppressed because it is too large Load Diff
+7 -10
View File
@@ -1,19 +1,16 @@
packages:
- "packages/*"
- "docs/"
allowBuilds:
esbuild: false
esbuild: true
sharp: true
onlyBuiltDependencies:
- playwright
supportedArchitectures:
os:
- current
- linux
cpu:
- current
- x64
libc:
- current
- glibc
os: [current, linux]
cpu: [current, x64]
libc: [current, glibc]