add new blog

HerringtonDarkholme · HerringtonDarkholme · commit 0ff7143bee5c · 2024-12-17T09:50:11.000-05:00
diff --git a/website/blog/typed-napi.md b/website/blog/typed-napi.md
@@ -0,0 +1,71 @@
+Improve Napi Typing
+
+What's type safety? Why?
+
+https://github.com/ast-grep/ast-grep/issues/1669
+https://github.com/ast-grep/ast-grep/issues/48
+
+It guides one to write comprehensive AST code (in case people forget to handle some cases)
+
+# TreeSitter's types
+
+Tree-Sitter's official API is untyped. However it provides static node types in json
+
+1. json hosted by parser library repo
+needs type generation(layman's type provider)
+2. contains a lot unnamed kinds
+You are writing a compiler plugin, not elementary school math homework
+3. has alias type
+
+
+# Big Idea
+
+1. lenient type check if no information
+2. more strict checking if refined
+
+
+# APIs
+
+## Prune unnamed kinds
+For example `+`/`-`/`*`/`/` is too noisy for a general AST library
+
+## `ResolveType<M, T>`
+
+Use type script to resolve type alias
+
+## `NodeKinds<M>`
+
+1. string literal completion with string
+2. lenient
+
+Problem?
+
+https://github.com/microsoft/TypeScript/issues/33471
+https://github.com/microsoft/TypeScript/issues/26277
+
+## Distinguish general `string` and specific kinds
+`RefinedNode<>`
+
+
+## Refine Node, Manually
+
+1.via `sgNode.find<"KIND">`
+2.via `sgNode.is<"KIND">`, One time type narrowing
+
+## Refine Node, Automatically
+
+`sgNode.field("kind")`
+
+
+## Exhaustive Checking via `sgNode.kindForRefinement`
+
+Only available specific kinds
+
+## Typed Rule!
+
+## Opt-in refinement for better compile time performance
+
+# Ending
+
+https://x.com/hd_nvim/status/1868453729940500924
+There are very few devs that understands Rust deeply enough and compiler deeply enough that also care about TypeScript in web dev enough to build something for web devs in Rust
