codebook

In that folder is CHANGELOG.md[0] that indicates that this is unreleased. I'd say that including installation instructions for an unreleased version of the extension is exactly the issue that is being flagged. [0] https://github.com/blopker/codebook/blob/main/vscode-extensi...

>I dunno, it seems to be real excited about a VS Code extension that doesn't exist and isn't mentioned in the actual documentation. There's just too many factual errors to list. There is a folder for a VS Code extension here[0]. It seems to have a README with installation instructions. There is also an extension.ts file, which seems to me to be at least the initial prototype for the extension. Did you forget that you started implementing this? [0] https://github.com/blopker/codebook/blob/c141f349a10ba170424...

Hey HN, I wanted to share a project I've been working on to help with my terrible spelling. CSpell is the thing everyone uses in VSCode, but they don't offer an LSP for other editors to use. Someone has made an LSP for it, but CSpell is also pretty slow since it's all in JavaScript. After spending way too much time[0] trying to find an alternative, I just wrote my own. Codebook[1] is written in Rust, so it's very fast, and (IMO) is much less annoying than CSpell because it uses Tree Sitter to only find spelling issues that the developer has control over. Codebook also comes with an LSP, so it could be used in other editors, but I haven't tried that yet. I want to also shout out to Spellbook[2], which is the actual spell checking engine I used to make Codebook. The makers of Helix wrote it, and it's fantastic. [0]: https://blopker.com/writ