TechTalk - 2o22 - JS/ TS/ React mistakes and how to avoid them

There are a lot of things that can go wrong with the way we use JS/TS. Here, we will talk about some applicable best practices along the way and some widespread mistakes

Transcript

1. JS/ TS/ React mistakes and how to avoid them
2. HypeTech Tech education and shaping ideas into hype products hypetech.io | reactweek.dev Marko Arsić Founder and CEO @ HypeTech Founder of HypeTech Education Lecturer @ ReactWeek.dev Independent Tech Consultant Helping companies set up teams and standardize the development process github.com/marsicdev
3. Each developer has to overcome troubles and obstacles That’s the job!
4. There are no exceptions here and each field is difficult and it seems rather hard to avoid mistakes at the very start.
5. General mistakes 🤕
6. We all fail to do this Planning Architecturing Documenting Testing Decoupling Automating
7. Not always, but more than often. It’s a fact !
8. JavaScript mistakes
9. Not understanding all ES features === vs == !! Optinals
10. Not understanding pure functions filter, map, reduce
11. Not using virtual properties in classes and private fields
12. Promise (chain, return types)
13. Some compare async/await with Promise and claim it is the next generation in the evolution of JavaScript asynchronous programming
14. async/await IS an improvement, but it is no more than a syntactic sugar, which will not change our programming style completely.
15. Async functions are still promises. You have to understand promises before you can use async functions correctly, most of the time you need to use promises along with async functions.
16. TypeScript mistakes
17. Not Enabling Strict Mode Without TypeScript strict mode on, the typing can be too lax, and that will make our codebase less type-safe. It will give the wrong impression, as some think that by adding TypeScript all typing issues are automatically fixed.
18. Redeclaring interfaces When typing component interfaces, it is common to need to have some different interfaces variants of the same type. Those can vary in one or two parameters. A common mistake is to manually redefine those variations. That will lead to: • unnecessary boilerplate. • multiple changes are needed if one property changes in one place, that change needs to be propagated to many files.
19. Not Relying on Type Inference TypeScript inference is one of the most powerful tools of this programming language. It does all the work for us. We only have to make sure that all the pieces add together with as little intervention as possible. A crucial operator to achieving this is the typeof.
20. Incorrect use of Overloading TypeScript supports overloading natively. That is great as it can improve the readability of our contracts. However, it is different from other typed overloading languages. There are scenarios where it might make our code more complex and verbose.
21. Using the Function Type TypeScript ships with the Function type. It is like using the any keyword but for functions only. Enabling strict mode won’t prevent us from using it. Function type: • accepts any number and type of parameters. • the return type is always any
22. Relying on a Third Party for Immutability TS provides all the necessary tooling to make sure we don’t mutate our objects. We don’t need to add heavy libraries like ImmutableJS to our codebase.
23. React mistakes
24. Decomposition / Decoupling
25. Decomposition / Decoupling
26. Modifying state directly
27. Setting new state that relies on the previous state without using a function
28. Forgetting that setState is asynchronous
29. Writing logic in components
30. Updatating state on unmounted component
31. Not creating enough components Creating to many components
32. Not handling errors
33. Not using prop-types when writing JavaScript
34. Not using absolute paths
35. Not using key on a listing component
36. Not using helper models, classes, functions or custom hooks (react-use)
37. Using X for absolutely everything / Using X unnecessarily
38. Not using Developer Tools
39. Summary
40. These guidelines are simple to follow and are meant to help you embrace ecosystem rather than fight it.
41. By applying these simple tips you will have a better, less verbose, and easy to maintain codebase.
42. Q & A As everything good in life, knowledge is great only when shared https://discord.gg/94uhCAkFKf
43. As everything good in life, knowledge is great only when shared hypetech.io/education
44. contact@reactweek.dev