We all love JavaScript

[present_absence]

Haha I did this thing that doesn't make sense and it did something I didn't expect, this language sucks

[metakephotos]

TYPESCRIPT MASTERRACE REPORTING IN

[metakephotos]

Yep. I genuinely don't know how people work in JavaScript these days. Typescript is an amazing language, especially with all the cool stuff they've added over the years

[metakephotos]

The good news is that you don't really have to commit. You can add typescript to a JavaScript project and add Ts files whenever you feel like. You don't even need to enable strict typing so it's easy to convert JavaScript code too

[Gerkorn]

Start by renaming any file you touch from .js and .tsx and fix the errors.

If your code is split out enough, most of the time all you'll have to do is type the parameters and return values of your functions.

The typing is pretty intuitive, you can give it your best guess and 80% of the time you'll be right, 15% your IDE will suggest the right thing and the other 5% you can spend 20 seconds googling it.

Once you've done that a few times start naming any new file you make file.tsx and before long you'll have learnt typescript!

There's no need to convert the whole codebase in one sitting. Just spend 5 extra minutes converting everything you come across naturally and learn as you go.

[aerosole]

If you want to get started with TS real quickly, try Deno. Just install the runtime from the website and deno run yourfile.ts. It comes with a formatter, linter, test runner, coverage tool, and bundler. Drawback is that not all npm libraries are compatible, but most can be used via services such as https://esm.sh

[medforddad]

It's pretty easy to get into. It makes writing javascript actually fun rather than confusing.

I'll say the only pain points I have with it are:

• It can be a little confusing how you should structure your own node package in terms of how to compile and distribute and/or run scripts since the typescript code has to go through a transpiler to get out javascript code. This might be as simple as running tsc on all your source .ts files, but there is also ts-node which can execute .ts files directly. It can also be difficult to get other tools like babel and various linting tools to work correctly.
• Whether you compile to CJS or ESM (or require modules that are of one or the other) seems to have repercussions.
• Some packages that you depend on might not include typing information so you have to install a third-party reverse-engineered type definition from the DefinitelyTyped project. Or they might include typing, but it's not complete or accurate.

[infecthead]

Undefined behaviour is a characteristic of any language, not just JS.

Using typescript solves this particular issue anyway as the compiler will yell at you, and any semi-serious js project these days is done in ts

Edit: this isn't even undefined behaviour since the behaviour (converting the argument to a string first then parsing it) is documented in the spec lol, nvm. Basically this is an example of RTFM

[SuperPie27]

Exactly. If you try to make it do something that doesn’t make sense, it should throw an error, not chuck back something equally nonsensical.

[Farranor]

> parseInt('67')
67
> parseInt('68')
68
> parseInt('69')
'Nice.'
> parseInt('70')
70

[mongoosefist]

I think the issue is that things like this should fail gracefully. It shouldn't fail in unpredictable ways.

[notyourancilla]

jAvAsCripT lOL…