Currently, if you parse a statement (create) on the client side using our parser and/or the WASM wrapper, you'll get back a normalized string that is intended to be consumed by the SQLite backend. It is not spec compliant, in that in may contain AUTOINCREMENT, STRICT, and other non-compliant SQL elements. These are implementations details. Ideally, we'd have a "spec safe" string method on the AST that would produce a parsed output that could be parsed again safely by the parser. This would make using the parser on the client side much easier, useful, and safe.
GSP-5