You should use ESLint and Prettier , which will warn you when you'll try to write unreadable and excessive code like this: !error.message ? err = {"message": error} : err = error; and change it like this: err = !error.message ? {"message": error} : error; There is even an ESLint rule for preventing using ternary operators all together: disallow ternary operators (no-ternary) The ternary operator is used to conditionally assign a value to a variable. Some believe that the use of ternary operators leads to unclear code. And that's for normal assignment usage, not even for procedural usage like you're doing in your code.

TypeScript is good for when creating projects that many people are going to contribute or libraries that many people are going to use, but for big/small one-man-show projects is such a waste of time writing all the typings and if you have enabled ESLint with some standard defaults, then you'll find yourself wasting countless minutes trying to satisfy TS compiler and linter especially when trying to convert JS code to TS and of course keep tsconfig options to strict typings mode. TypeScript is awesome for DX and when many people are involved in one project but for larger projects it's going to bloat the code and it doesn't provide much on bug catching; proper testing should always be present in all projects small or big ones , and that's what prevents bugs mostly. There is even a ESLint rule for requiring PropTypes when optional props do not have default values react/require-default-props and it does appear in TS projects as well and it actually makes sense.

Nice guide for using Firebase Vision ML API in a React Native application 👍 You should also add a section about the GC Vision ML pricing , which is $1.50 per 1000 units/images after the first free 1000 units/month. Cloud pricing and costs is something that it should be taken very seriously to avoid pitfalls and disastrous huge CC charge situations like this How NOT to get a $30k bill from Firebase .

It's a nice python tutorial for beginners to learn how to work with strings and random bytes 👍, but there are already countless online password generators for everyday use. For example, you can check mine at my blog which works online, is fully customizable and it can generate hundreds or thousands of random passwords based on multiple parameters like uppercase characters, lowercase characters, numbers, symbols, excluding characters, password length and how many passwords to generate in individual text boxes or in one big text area to contain them all. There are also CLI tools for generating passwords if you want to use it in command line, like ts-pwgen which has many options to generate custom password.

Nice article Madza . shortid is now deprecated and they suggest the amazing Nano ID as an alternative. The title concept is not future proof! What if you need to add more tools to that list? You'll have to rename and change 73 for both the title and the slug url, which will lead to lose the SEO of the article and direct links to it will be broken! Also, you should not hardcode counters like you do from 1 to 73, you can use CSS counters to have automated and customized counters and don't have to re-arange the numbers each time you remove or add something. I have copied your article to my blog and I wrote a mention to this page and your blog at the very beggining https://lytrax.io/blog/dev/awesome-npm-packages-for-productivity. Thanks for collecting all of the packages and the short descriptions into one article.