Idea for preview: use pandoc compiled to wasm instead of markdown-it.js
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 66
- PR merge metrics
- No merged PRs in 30d
Description
see https://pandoc.org/app/ evaluate performance
could we also use it for export instead of shelling out to the pandoc CLI?
Edit: alternatively, we could try:
- spawning pandoc-server in a separate process and see how bad latency is... using a websocket instead of separate HTTP requests could help, but maybe HTTP/2 is just as good.
- pulldown-cmark compiled to wasm
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no project files or tests. Start by benchmarking the current markdown-it.js preview and pandoc CLI export, then compare pandoc compiled to WASM, pandoc-server, and pulldown-cmark compiled to WASM, including the proposed WebSocket or HTTP/2 communication. Done would require selecting an approach and reporting performance, but no success threshold is defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, typescript, wasm
- Domain
- desktop, frontend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100