Re:Finally, a guide for Node.js and TypeScript and ESM that ...
by azangru on Tuesday November 21, 2023 @07:54AM
(#38363017)
> a working example that you don't understand and just copy over and over again into new projects.
Once you have a working example, you can go through it line by line and figure out what it is doing.
Re:Finally, a guide for Node.js and TypeScript and ESM that ...
by Feathercrown on Tuesday November 21, 2023 @09:52AM
(#38364375)
Which the author would be kind to do and post with the example.
Re:Finally, a guide for Node.js and TypeScript and ESM that ...
by mst on Tuesday November 21, 2023 @11:23AM
(#38365739)
Honestly, I've always preferred to have somebody's example plus the reference documentation.
Learning not only what it does but where it's documented - and having to go look for myself to do so - fixes it in my memory a lot better.
I have a years old set of npm/etc. configs in a project I noodle on occasionally, and when I re-open them to look I remember exactly what they do -because- I started from a boilerplate and then went and learned how all of it works.
That doesn't mean an explanation wouldn't still be helpful for a bunch of people who aren't me, but honestly having the tsconfig commented like that is more than sufficient for -me- to be happy.
This eventually turns into an incantation and magic. It's how crap gets built up and poor decisions get propagated.