Summary
fastled-wasm should migrate to fastled/cli as its new home.
Rationale
- Consolidates FastLED's command-line tooling under the official
fastled GitHub organization.
- Aligns the WASM compiler with the broader FastLED CLI surface (compile, flash, autoresearch, etc.) rather than keeping it siloed under a personal namespace.
- Gives users a single canonical entry point for FastLED CLI workflows.
Scope
- Move the repository / codebase to
fastled/cli (new repo) as the WASM subcommand, or merge functionality there.
- Update package name, PyPI distribution, and install instructions.
- Redirect issues and pin a migration notice on
zackees/fastled-wasm.
- Update all documentation and cross-links in the main
FastLED/FastLED repo that reference zackees/fastled-wasm.
Open questions
- Preserve
zackees/fastled-wasm as an archived mirror, or fully deprecate?
- Single
fastled CLI with subcommands (fastled wasm, fastled compile, ...) vs. per-tool binaries?
- PyPI package rename strategy — deprecate old, publish new, or transitional meta-package?
Summary
fastled-wasmshould migrate tofastled/clias its new home.Rationale
fastledGitHub organization.Scope
fastled/cli(new repo) as the WASM subcommand, or merge functionality there.zackees/fastled-wasm.FastLED/FastLEDrepo that referencezackees/fastled-wasm.Open questions
zackees/fastled-wasmas an archived mirror, or fully deprecate?fastledCLI with subcommands (fastled wasm,fastled compile, ...) vs. per-tool binaries?