dev
Cultivating curiosity for software developers
veganbeef pfp
4 replies
5 recasts
14 reactions

Arti Villa pfp
1 reply
0 recast
1 reaction

Arti Villa pfp
0 reply
0 recast
0 reaction

downshift πŸŒΉβ³πŸ’€ pfp
0 reply
0 recast
5 reactions

caso pfp
3 replies
0 recast
16 reactions

agusti pfp
2 replies
0 recast
3 reactions

Arti Villa pfp
3 replies
0 recast
6 reactions

Arti Villa pfp
In most worlds, I would not bother checking what the "Node16" module resolution settings pertain to, but with LLMs, I feel like I just get educated way more. In fact, I actually knew what the resolution change meant, but I didn't know it changed in version 16 and this is the point of entry to read. protip: I've asked LLMs to explain configuration files as I come across them. It would be overwhelming to learn all of them in a single go, but as I read more, I get more familiarity with different project structures. If you think people are getting dumber, don't hate the tool, hate the player. ``` The "Node16" setting in TypeScript: When you set "moduleResolution": "Node16" , TypeScript understands these new rules and will: β€’ Check your package.json "type" field β€’ Enforce proper file extensions β€’ Handle both CommonS and ES modules correctly It's like telling TypeScript: "Hey, use the smart new way Node.js figures out modules, not the old simple way." ```
0 reply
0 recast
3 reactions

Arti Villa pfp
0 reply
0 recast
0 reaction

tani pfp
1 reply
1 recast
5 reactions

Josh Ellithorpe pfp
1 reply
0 recast
4 reactions

tani pfp
4 replies
1 recast
10 reactions

Royal pfp
0 reply
0 recast
2 reactions

Royal pfp
1 reply
0 recast
1 reaction

Royal pfp
0 reply
0 recast
3 reactions