Skip to content

TODO.md

Latest commit

 

History

History
119 lines (99 loc) · 7.34 KB

TODO.md

File metadata and controls

119 lines (99 loc) · 7.34 KB
Raw

TODO — helpers4/typescript

Last refresh: 2026-07-21.

Legend: 🔴 High priority · 🟡 Medium · 🟢 Low

Only open items live here. Anything finished is in git history / CHANGELOG.md / MIGRATION.md, not duplicated in this file.

AI-friendliness / discovery

  • 🟢 List helpers4 on general (non-AI) TypeScript discovery sites — the previously-suggested target (dzharii/awesome-typescript) is archived/read-only as of 2026-02-11. Needs a currently-maintained curated TS list found and confirmed active first.
  • 🟢 Package /add-helper (or the consumer-facing skill below) as a real Claude Code plugin and submit to anthropics/claude-plugins-official — only makes sense for the consumer-facing skill; /add-helper is project-scoped and gains nothing from external listing.
  • 🟢 Consumer-facing Claude Code skill (not built — needs a design pass): unlike /add-helper (helps people contribute to this repo), this would help people using @helpers4/* avoid reinventing a utility that already exists here.
    • Source of truth: the per-package llms.txt already generated at build time — no new data pipeline needed.
    • Distribution is the hard part (same blocker as the outreach item below): needs an actual channel — a plugin/marketplace listing, or a CONTRIBUTING.md/README install step — not just dropped in this repo's .claude/skills/, which only reaches people already working in this repo. Worth prototyping once that channel exists, not before.

Contributors / outreach

Blocked while the project is solo. One regular collaborator unlocks the Code-Review Scorecard check (~+2 pts) and makes human review possible.

  • 🔴 Mention the project across TS/JS communities — outreach, not something an agent can do on the maintainer's behalf. Checked 2026-07-21, concrete targets:
    • PR to sorrycc/awesome-javascript (active, last push same day) — one entry, [PACKAGE](LINK) - DESCRIPTION. per its CONTRIBUTING.md. Also covers LibHunt for free — it auto-indexes from this exact list, no separate submission there.
    • Post to r/typescript + r/javascript, Discord, X/Twitter.
    • Write a "Why Helpers4?" article, cross-post to Dev.to + Hashnode + LinkedIn.
    • Show HN — one-shot and timing-sensitive (can't really redo it), but real upside if the article above gives it something to point to.
    • DevHunt (dev-tool-focused Product Hunt alternative, PR-based submission) instead of Product Hunt itself — Product Hunt expects a fresh-launch narrative that a library shipped as v3 months ago doesn't have; DevHunt doesn't.
    • Add relevant GitHub Topics tags to the repo (typescript, utility-library, …) — free, self-service, no external submission.
    • Checked and rejected, don't re-research these: Openbase (shut down 2023, domain dead), Open Source Agenda (domain expired, now redirects off-site), npmcompare.com (unreachable), "JS Toolbox" and "Perf-Track JS" (no such submittable sites exist), StackShare (built for companies listing their stack, not devs promoting a library), BetaList (explicitly pre-launch-only by their own criteria — disqualified), Indie Hackers (monetization-focused community, OSS-lib posts are off-topic), Lobsters (invite-only, drive-by self-promo gets flagged — only viable via genuine organic participation, not as a submission channel), "Claude/Agent Skills Marketplace" (not a real distinct product, and out of scope anyway — helpers4 is a TS library, not a Claude plugin).
  • 🟡 Once a regular reviewer joins: raise required_approving_review_count to 1 on main, record evidence (URL/reviewer/timestamp) per merged PR — unlocks Code-Review scoring.

OpenSSF Scorecard

Live score: curl -s https://api.securityscorecards.dev/projects/github.com/helpers4/typescript.

  • 🟡 Token-Permissions and Branch-Protection fixes (PRs #108/#109) are unverified against the live repo config — gh api repos/helpers4/typescript/rulesets returned [] on 2026-07-19, but the token used lacks admin rights to tell "no rules" from "no permission to see them." Needs a maintainer check with an admin token.
  • 🟢 CII-Best-Practices Silver/Gold — deferred, needs sustained contributor activity.

Code quality & tooling

  • 🟡 Browser compatibility gap: the Temporal-based date helpers (ensureDate, range, timeAgo, formatDuration, timezone + 6 guard/isTemporal*) claim ES2022+ support but Temporal isn't in ES2022 and Safari has no stable support yet (WebKit signals "late 2026"). CI never tests an actual browser. Needs a maintainer decision: document the Safari caveat, scope the browser claim down, or accept a polyfill as an optional peer dependency for date/guard.
  • 🟡 .d.ts emit blocked on TypeScript 7: rollup-plugin-dts needs the classic Compiler API, which TS 7.0's main export no longer exposes at all outside unstable/*. Tracked upstream at Swatinem/rollup-plugin-dts#395 (maintainer has a working fix on a branch, not yet merged). Revisit once that ships, or once TS 7.1 delivers a stable new API.

Future / needs design discussion

  • 🟢 New "settings" package for shared tool configs (vite/vitest/oxc/lint/cspell…), customized for helpers4/baxyz instead of a third-party preset. Not a helpers/ category — configs don't tree-shake like functions — needs a design decision on package/repo shape before implementation.
  • 🟡 Cross-category name collisions: isEmpty alone exists as array/isEmpty.ts, object/isEmpty.ts, and string/isEmpty.ts (verified 2026-07-26) — fine as long as each category is imported separately, but a real problem the moment anything flattens them into one namespace (@helpers4/all, a future import * as h4, etc.). Idea: also publish each helper under a category-suffixed alias (isEmpty4Array, isEmpty4Object, isEmpty4String) alongside the plain name, so collision-prone call sites have an unambiguous escape hatch without forcing everyone to use the suffixed form. Needs a design pass: which helpers actually collide (audit first, don't guess), where the alias is generated (build step vs. hand-written export), and whether it's worth the doubled public API surface for names that don't collide.
  • 🔴 @helpers4/all doesn't actually install the whole library: checked .template/bundle/package.json (2026-07-26) — it lists every category as a peerDependency, not a dependency, and ships no JS at all (no main/exports, files is just LICENSE.md/package.json/README.md/meta//llms.txt). peerDependencies aren't auto-installed by pnpm by default, and even fully installed there's no code in the package to import from — so @helpers4/all today is a metadata shell, not a working "install everything" package. Needs a real fix: likely re-exporting every category's index.ts as dependencies (not peer) with an actual bundled lib/index.js, generated the same way each category's own bundle already is — check buildBundle/prepareBundlePackageJson in scripts/build/build-bundle.ts for where this needs to change.