I'm actually using JSTypes in app, I don't mind it. I choose to use it because I didn't want to deal with a build step for a smaller project. The project has g

I'm actually using JSTypes in app, I don't mind it. I choose to use it because I didn't want to deal with a build step for a smaller project. The project has grown and I am looking at adding a build step for bundling but still not too worried about using JSDoc over TS. This might be my config, but one thing that does annoy me is whenever I define a lambda, I need to add an doc type. I guess if that's disincentivising me from writing lambdas maybe I should just add a TS compile step lol. ---------------------- Here's an example - I got some config typed with this function https://github.com/AKST/analysis-notebook/blob/c9fea8b465317f41da2a10d7c1d493c811803e32/lib/app/sec-unsw/sec-2102/sec-05-3/util.js#L11-L14 https://github.com/AKST/analysis-notebook/blob/c9fea8b465317... - Here's the type https://github.com/AKST/analysis-notebook/blob/c9fea8b465317f41da2a10d7c1d493c811803e32/lib/app/sec-unsw/sec-2102/sec-05-3/type.ts#L18-L36 https://github.com/AKST/analysis-notebook/blob/c9fea8b465317... - And here's something to generate a more complicated type for defining config knobs https://github.com/AKST/analysis-notebook/blob/c9fea8b465317f41da2a10d7c1d493c811803e32/lib/base/runtime/config/type.ts#L52-L60 https://github.com/AKST/analysis-notebook/blob/c9fea8b465317...