apexgantt 3.17.2 → 3.18.1

package/LICENSE

@@ -0,0 +1,116 @@
+## 📄 License Options for ApexGantt
+
+ApexGantt is offered under a **dual-license model** to support individuals, startups, and commercial products of all sizes.
+
+One license key works across every Apex product, so a customer of one does not buy a second for another.
+
+---
+
+### 🔓 Community License (Free)
+
+For individuals, non-profits, educators, and small businesses with **less than $2 million USD in annual revenue**.
+
+✅ What's allowed:
+
+- Personal, educational, or non-profit use
+- Commercial use by small orgs (under $2M annual revenue)
+- Modifications, and redistribution of the library itself (with attribution)
+
+🚫 Not allowed:
+
+- Use by companies or entities over $2M/year revenue
+- Use in competing charting or project scheduling products
+- Sublicensing under different terms
+- Embedding in a product or platform used by other people, which needs the OEM License below whatever your revenue
+
+➡ By using ApexGantt under this license, you confirm that **you qualify as a Small Organization**.
+
+---
+
+### 💼 Commercial License (Paid)
+
+The Commercial License applies to all paid SKUs (Pro, Premium and OEM).
+
+The **Community License** is available at no cost **only** to organizations with **annual revenue under $2M USD**.
+If your organization earns $2M USD or more annually, you must purchase one of our paid licenses.
+
+Pro and Premium are priced per developer, and priced on the features you use rather than on your revenue.
+
+✅ What's included:
+
+- Use in internal tools and commercial applications
+- Modifications and app-level distribution
+- 12-month subscription with updates & support
+
+🚫 Not allowed:
+
+- Redistribution in toolkits, SDKs, or platforms
+- Use by unlicensed developers
+- Competing charting or project scheduling products
+
+---
+
+### 🏛 Non-Profit Tiers
+
+Non-Profits are treated like commercial entities:
+
+- Annual operating budget **less than $2 million USD**
+- _Eligible for Community licenses_
+
+or
+
+- Annual operating budget **greater than $2 million USD**
+- _Commercial license with possible discounts for Community, Pro, Premium and OEM products_
+
+---
+
+### 🔄 OEM / Redistribution License (Paid)
+
+Required if you are **embedding ApexGantt into a product or platform used by other people**, such as:
+
+- No-code dashboards
+- Developer platforms
+- Embedded BI tools
+- SDKs
+
+✅ What's included:
+
+- Redistribution rights for **one application or product**
+- **Unlimited developer seats** on that application, with no separate per-developer license to buy
+- **Every licensed feature**, at the highest tier
+- 12-month subscription with updates & support
+
+Your end users need no license of their own. A second application needs a second OEM license. White-label, resale, and affiliate arrangements are quoted separately.
+
+✅ OEM **not required** if your app simply renders static charts and users **cannot** configure or interact with them.
+
+---
+
+### ⏳ When a subscription ends
+
+Your license key expires, and **licensed features render with a trial watermark**. You no longer receive updates, new features, or technical support. Work built only from free features is unaffected, and your existing deployment keeps running.
+
+For OEM licenses, continued redistribution requires an active subscription.
+
+---
+
+### ⚠️ License Acceptance
+
+By installing ApexGantt (e.g., via `npm install apexgantt`), you are agreeing to the applicable license based on your usage:
+
+- Community License (if under $2M revenue)
+- Commercial License (if over $2M revenue)
+- OEM License (if redistributing to third-party users)
+
+---
+
+### 🛠 Need a License or Have Questions?
+
+📧 Contact us at [sales@apexcharts.com](mailto:sales@apexcharts.com)
+📚 Read full license agreements here: [https://apexcharts.com/license](https://apexcharts.com/license)
+
+---
+
+Copyright © 2026 ApexCharts. All rights reserved.
+
+Thank you for supporting ApexGantt! Your licensing helps keep it free and open for individuals and small teams.

package/README.md

@@ -1419,3 +1419,56 @@ function GanttChart({tasks}) {
   return <div ref={containerRef} />;
 }
 ```
+
+## Family theme tokens (`--apx-*`)
+
+Every chart in the ApexCharts family reads the same five root tokens, so a page can state its brand once and have trees, flow diagrams, Gantt charts and plots all follow:
+
+| Token                               | Role                                                             |
+| ----------------------------------- | ---------------------------------------------------------------- |
+| `--apx-accent`                      | The colour that means interactive or selected                    |
+| `--apx-fore`                        | Text and anything that must stay legible on the surface          |
+| `--apx-grid`                        | Hairlines: borders, gridlines, connectors                        |
+| `--apx-surface`                     | The plane content sits on                                        |
+| `--apx-series-1` … `--apx-series-N` | An ordered categorical palette (1-based, stops at the first gap) |
+
+```css
+:root {
+  --apx-accent: #5b21b6;
+  --apx-fore: #101828;
+  --apx-grid: #e4e7ec;
+  --apx-surface: #ffffff;
+}
+
+@media (prefers-color-scheme: dark) {
+  :root {
+    --apx-fore: #f8fafc;
+    --apx-grid: #334155;
+    --apx-surface: #0f172a;
+  }
+}
+```
+
+Custom properties inherit, so declaring them on `:root` reaches every chart on the page. They resolve **below anything you configured explicitly**, so adopting them cannot change a chart that was already themed:
+
+```
+product CSS variable  >  explicit option  >  --apx-* token  >  built-in default
+```
+
+An option set to a value equal to its built-in default is indistinguishable from one left alone, and the token wins there. Set a product variable if you need a value pinned regardless.
+
+### Named themes
+
+`registerTheme` from `@apex/commons` records a named set of tokens on a registry shared by the whole family, so a brand theme registered once from any product is resolvable by name from all of them:
+
+```js
+import {registerTheme} from '@apex/commons';
+
+registerTheme('acme', {
+  tokens: {accent: '#5b21b6', fore: '#101828', grid: '#e4e7ec', surface: '#ffffff'},
+});
+```
+
+A named theme's tokens sit one layer below the CSS `--apx-*` tokens, so the cascade still wins over the registry.
+
+Gantt reads the CSS `--apx-*` tokens directly. It has no theme-name option, so the named-theme layer does not apply to it; use the CSS tokens (or a `prefers-color-scheme` block over them) to theme it alongside the rest of the family.