This article is not something you might not already know but maybe you might not have it all listed in a one place. There can be more things that I...
For further actions, you may consider blocking this person and/or reporting abuse
What if we have a single logger service and check the environmnt?
Can you please elaborate?
For number 1. We don't want to log in our console in production. We can create a singleton service and check the environment before logging. By this we followed SRP too..
Nice one. Can you please write an article on it. Or maybe I'll do it when I'm done curating the other articles on my list 😃
I'd love to, but am so busy these days... I'm sure you'll write a good one until i want to start :)))
Thanks much for posting this.
Welcome Manisha.😀
Thanks for commenting. It keeps me fueled up for writing more of such posts.
Sure, appreciate such endeavours always and would love to contribute too.
I'm pretty sure that 1,2 and 3 is been done by webpack (or the responsible plugin) I mean who on earth would delete ALL comments before a production build in ALL files, the comments are there for (almost) a good reason?
Yes Paul. The production build is optimized and the points 1,2, and 3 are handled. However, removing those files that are not in need is also helpful in the sense that if other devs get through your project they don't have to scratch their head to find the reason for their existence. And having these processes already done may improve the time it takes to make the build.
But you are spot on with your pick. Thanks for that.
Do you have any point that you would like to add which we as a dev can do?
Super useful tips! I was just going to build an app for production and didn't even know some of these. Thank you...
I'm super glad to know that the post reached to someone who really was in the same stage. Happy production deployment.😄
Super useful tips! Thank you!
for 1 and 2 steps, you could use linting rule for avoid getting that.