Meet the team
See all 2 on GitHub →
Commit activity
Last 12 weeks · 0 commits
Community health
3 of 6 standards met
62
✓README○License✓Contributing✓Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Quiet · 3 in progress · Last activity 3y ago
See all on GitHub →
First, cleaning up types before porting data over. This aims to make types (and lists of values) easy to consume e.g. in solid-site. Replace enums with arrays (for easy enumeration in JS plus automatic types) Split vs. ( for the union). Are we happy with this terminology? (It matches solid-site's current notation.) Drop option for Packages. We discussed this a long time ago; I don't think there's a useful distinction between and . (I could still see calling the merged type ...) Switch from Unix timestamps to ISO date times Rename into . ?? Should we split into and ? It looks like is the one and only one used by resources. It's also used in one package, so I guess it could be listed twice... Add annotations and script for generating JSON schema! generates . Second, restructure to use individual JSON files in . is no longer in the repo but is still in the JSON export. Many more scripts.
Structured data for AI agents
Repository: solidjs/solidex. Description: Solidex is a list of SolidJS ecosystem resources and packages. Stars: 16, Forks: 4. Primary language: TypeScript. Languages: TypeScript (100%). Open PRs: 3, open issues: 1. Last activity: 3y ago. Community health: 62%. Top contributors: davedbase.