[ ] 2. Debatable. Current Native lib types chain without lib/apis.all.d.ts on top of (1). Replacement types, not overrides. For real-time types during development phase of Native lib api for lo or user project. Ideally need this feature to pick lib/<name>/api.js with lo.load/lo.library(<name>) so won't need to search file system for relevant names beforehand
[ ] 3. globals.d.ts segments:
[ ] 3.1. User types
[ ] 3.2. (1.2)
[ ] 3.3. Base types
[ ] 3.4. (1.1) and other autogenerated stuff
[ ] 3.5. (2). Generate segment using lo type <config.js path> --dev or something like that. Empty as first step before build (maybe just find offset to exclude segment from embed). Expose relevant method(s) in lib/types.js
Current dynamic type chains
Native lib types:
lib/<name>/api.js=>lib/apis.all.d.ts=>globals.d.tsImports:<some path>.d.tsor<some path>.jsCurrent type generation file
lib/types.jsWants:
globals.d.ts:declare "lib/<name>.js" { ... }types forlib/<name>.jsDebatable. Current Native lib types chain withoutlib/apis.all.d.tson top of(1). Replacement types, not overrides. For real-time types during development phase of Native lib api forloor user project. Ideally need this feature to picklib/<name>/api.jswithlo.load/lo.library(<name>)so won't need to search file system for relevant names beforehandglobals.d.tssegments:(1.2)(1.1)and other autogenerated stuff(2). Generate segment usinglo type <config.js path> --devor something like that. Empty as first step before build (maybe just find offset to exclude segment from embed). Expose relevant method(s) inlib/types.js