jcbhmr

JSDoc works great for buildless application setups! One downside is that if you publish a library to npm you still need a build step to generate .d.ts files from your JSDoc type annotations so that npm shows a "TS" badge on the npm package page. This also seems to apply to VSCode's intellisense which keeps trying to poke you to "try to install @types/jsdoc-typed-package to get type information". Other JS ecosystem tooling also doesn't seem to process JSDoc types at all such as jsdocs.io or tsdocs.dev. So for libraries we're stuck with .d.ts generation via "tsc --allowJs --checkJs --declaration ..." even if it's all JS.

npm displays packages with bundled TypeScript declarations https://github.blog/changelog/2020-12-16-npm-displays-packag...

JSDoc-typed node modules require special configuration in consumers to be useful https://github.com/microsoft/TypeScript/issues/19145

Star Wars: Revenge of the Sith by Matthew Stover

https://doc.rust-lang.org/cargo/reference/unstable.html#scri...

Lets you do this:

    #!/usr/bin/env -S cargo +nightly -Zscript
    ```cargo
    [dependencies]
    clap = { version = "4.2", features = ["derive"] }
    ```
    
    use clap::Parser;
    
    #[derive(Parser, Debug)]
    #[clap(version)]
    struct Args {
        #[clap(short, long, help = "Path to config")]
        config: Option<std::path::PathBuf>,
    }
    
    fn main() {
        let args = Args::parse();
        println!("{:?}", args);
    }