You could also create a shortcut script in your package.json
5. [BONUS] if you want your code to be validated before every commit you can do that with the help of `lint-staged` (github.com/okonet/lint-st…):
Just install it into your project with:
```
npx mrm lint-staged
```
6. [BONUS 2] You can install the eslint plugin for your favourite editor and enable the option "Format on save" to have your code automatically fixed as you type! ✨👨💻
I hope this is useful! Let me know what your setup looks like 🤓
(apparently this time I managed not to break the thread, SUCCESS 🥳)
How many times did you have to store settings (creds & other preferences)? Where do you save the conf file? Which format do you use? How do you load and update the file?
Conf takes care of all of this (and more!) with an extremely simple API
"Yo, why are #JavaScript and its ecosystem so messy?!" 😡
Well, I am glad you asked... Let me tell you a story! 🤓
🧵👇
For starting... #JavaScript was not designed to be the language that it is today!
JS was created in 1995 by @BrendanEich for Netscape, a web browser that was trying to come up with a language to make the web more interactive
@BrendanEich#JS wasn't related w/ #Java, so why did they call it Java-Script?! Duh! 😳
Java was trendy! it was possible to build interactive sites by embedding Java apps in pages (applets). So it was mostly a #mktg move: "JS: the lightweight Java alternative" or something like that I guess
This is easy and it works! But the implementation is very specific to our struct.
The rest of the codebase doesn't really know that this type can be converted to a String and therefore you cannot build abstractions on top of this... 🤨
1️⃣ You can't tell where a program is going to spend its time. Bottlenecks occur in surprising places, so don't try to second guess and put in a speed hack until you've proven that's where the bottleneck is.
2️⃣ Measure. Don't tune for speed until you've measured, and even then don't unless one part of the code overwhelms the rest.