Starting a TypeScript Project in 2021

Post by imjared » Wed, Apr 21, 2021, 2:44 PM UTC

rossng wrote: post #14

nikivi wrote: post #2

Nice article, you could also just use https://github.com/formium/tsdx

I looked at TSDX for a project and was rather put off by the fact that: * It hasn't been updated for six months * It doesn't appear to support TypeScript 4 properly[1] [1] https://github.com/formium/tsdx/issues/926

Post by evv » Wed, Apr 21, 2021, 2:53 PM UTC

rossng wrote: post #14

nikivi wrote: post #2

Nice article, you could also just use https://github.com/formium/tsdx

I looked at TSDX for a project and was rather put off by the fact that: * It hasn't been updated for six months * It doesn't appear to support TypeScript 4 properly[1] [1] https://github.com/formium/tsdx/issues/926

Post by GORRILA » Wed, Apr 21, 2021, 3:09 PM UTC

meheleventyone wrote: post #29

dtech wrote: post #27

Earlier quoted context omitted.

Linting is not the same as typechecking. Take a look at the default available rules [1]. For example number == NaN is valid Javascript, but 99.9% of the time an error. Or you might want to require always using === over ==. Generally, linting is things that are valid in the language, but still better to do otherwise. [1] https://eslint.org/docs/rules/

I’m aware of the difference just wondering what benefits people have found. Catching == versus === is a good one.

Post by mannanj » Wed, Apr 21, 2021, 3:11 PM UTC

andrew_ wrote: post #22

wa1987 wrote: post #20

Earlier quoted context omitted.

> Please stop spreading this misnomer. That's a fairly… direct way of putting it :-) Anyway: 1. What are the key differences in terms of usage and use cases? 2. Why isn't Deno a 'wholesale' replacement for Node? 3. In which respect are the vastly differently inner workings relevant in regards to usage of both products?

I suspect the reply was snide, masked by a smiley face, but here ya go anyhow. First result on Google for "deno vs node" https://www.imaginarycloud.com/blog/deno-vs-node/#:~:text=Wh... ) that covers the basics of all three asked points.

Post by austincheney » Wed, Apr 21, 2021, 3:24 PM UTC

    // module commandName is a module to parse a command, exclusion list, and options apart from other arguments of process.argv
    import commandName from "./lib/terminal/utilities/commandName.js";
    // module commandList is the list of modules that serve as commands for your application
    import commandList from "./lib/terminal/utilities/commandList.js";
    // module command_documentation provides documentation to the terminal about your commands and each of their options
    import commands_documentation from "./lib/terminal/utilities/commands_documentation.js";
    // module vars is a generic configuration store available across the application
    import vars from "./lib/terminal/utilities/vars.js";
    
    (function terminal_init_execute():void {
        // command documentation
        vars.commands = commands_documentation;

        // supported command name
        vars.command = commandName() as commands;

        commandList[vars.command]();
    }());

    node myApplication myCommand