23 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
28 changed files with 1065 additions and 5074 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
+27 -20
View File
@@ -2,20 +2,22 @@ name: CI
on:
push:
branches: ['*']
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
- uses: actions/setup-node@v4
with:
node-version: "22"
- run: corepack enable
- run: corepack prepare pnpm@11.11.0 --activate
@@ -29,15 +31,16 @@ jobs:
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
- uses: actions/setup-node@v4
with:
node-version: "22"
- run: corepack enable
- run: corepack prepare pnpm@11.11.0 --activate
@@ -49,13 +52,14 @@ jobs:
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
- uses: actions/setup-node@v4
with:
node-version: "22"
- run: corepack enable
- run: corepack prepare pnpm@11.11.0 --activate
@@ -66,18 +70,21 @@ jobs:
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
- uses: actions/setup-node@v4
with:
node-version: "22"
- run: corepack enable
- run: corepack prepare pnpm@11.11.0 --activate
- run: pnpm install --frozen-lockfile
# ========================================================
- name: Run component tests (Docker)
run: pnpm test:component
- 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
}
+8 -13
View File
@@ -50,7 +50,9 @@ luna-charts/
├── .changeset/ # Release/versioning configuration
── .github/ # Community health files (Code of Conduct, etc.)
── .github/ # Community health files (Code of Conduct, etc.)
└── .gitea/ # CI workflows (Gitea Actions) and CI runner image
```
## Getting Started
@@ -86,19 +88,12 @@ pnpm install
| `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 |
### Storybook
Storybook currently needs to be started from within the library package directly:
```bash
cd packages/luna-charts
pnpm run storybook
```
> **Note:** Running Storybook from the repository root isn't set up yet. This is a known gap — contributions to add a root-level `pnpm --filter` script are welcome.
Component and browser tests run inside Docker (`docker-compose.test.yaml`) to guarantee a reproducible browser environment across all contributors and CI — you don't need Playwright browsers installed locally.
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
-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$",
},
],
},
},
];
+12 -3
View File
@@ -5,12 +5,13 @@
"main": "index.js",
"scripts": {
"docs": "pnpm --filter docs run dev",
"lint": "eslint .",
"lint": "pnpm --filter luna-charts run lint",
"format": "prettier --write .",
"format:check": "prettier --check .",
"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"
@@ -32,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.
*/
+3
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",
+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,10 +1,7 @@
# my-component
<!-- Auto Generated Below -->
## Properties
| Property | Attribute | Description | Type | Default |
@@ -13,7 +10,6 @@
| `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();
+730 -587
View File
File diff suppressed because it is too large Load Diff
+4 -9
View File
@@ -10,12 +10,7 @@ onlyBuiltDependencies:
- playwright
supportedArchitectures:
os:
- current
- linux
cpu:
- current
- x64
libc:
- current
- glibc
os: [current, linux]
cpu: [current, x64]
libc: [current, glibc]