Meet the team
See all 2 on GitHub →Commit activity
Last 12 weeks · 0 commits
Community health
3 of 6 standards met
Recent PRs & issues
Adds to Solidex's package resources. is the SolidJS 1.9 / SolidStart renderer in the Markstream family. It is designed for AI chat and SSE/WebSocket Markdown streams, handling incomplete Markdown while tokens arrive, streaming code blocks, Mermaid, KaTeX, safe HTML, and long responses. This complements the existing and entries by focusing on incremental AI/chat rendering. Package: https://www.npmjs.com/package/markstream-solid Solid guide: https://markstream.simonhe.me/frameworks/solid API reference: https://markstream.simonhe.me/guide/solid The change only updates and follows the existing shape.
Hi maintainers, I would like to propose adding markstream-solid to Solidex's package resources. Package: https://www.npmjs.com/package/markstream-solid Project: https://github.com/Simon-He95/markstream-vue Solid guide: https://markstream.simonhe.me/frameworks/solid API reference: https://markstream.simonhe.me/guide/solid markstream-solid is a SolidJS 1.9 / SolidStart renderer for AI chat and SSE/WebSocket Markdown streams. It keeps incomplete Markdown readable while tokens arrive and supports streaming code blocks, Mermaid, KaTeX, safe HTML, and long responses. This is distinct from finished-document renderers such as solid-markdown and solid-marked because it focuses on incremental AI/chat output. I understand the README asks contributors to modify resources/ and submit a PR. I am opening this proposal to confirm the appropriate package category and entry format before preparing the PR. Thank you!
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.
Repository: solidjs/solidex. Description: Solidex is a list of SolidJS ecosystem resources and packages. Stars: 18, Forks: 4. Primary language: TypeScript. Languages: TypeScript (100%). Open PRs: 4, open issues: 2. Last activity: 4y ago. Community health: 62%. Top contributors: davedbase.