Protect your javascript source code

Your source code is public if you don’t know this simple trick:

When you build your project, the process generates a folder called “build” or any other as per framework policy. Just go to the build folder, and you will find some .jsextension files, and some are .map extension files. The js & map files are the source and map files. The map files are also important while developing. The map helps to debug.

There are two simple solutions to solve the problem. The ultimate target is to remove map files before deployment. Here is a simple way you can use it. Add GENERATE_SOURCEMAP = false at your package.json script section.
“scripts”: {“build”: “GENERATE_SOURCEMAP=false}
Removing maps manually will also work, but this is now a proper way.

GIT – How to remove node_modules

Create a .gitignore file in the git repository if it does not contain one
touch .gitignore

Open up the .gitignore and add the following line to the file

Remove the node_modules folder from the git repository
git rm -r –cached node_modules

Commit the git repository without the node modules folder
git commit -m “Removed node_module folder”

Push the repository to github
git push origin master

After all of that, you should also add the gitignore and commit it to the repository

git add .gitignore

git commit -m “Updated the .gitignore file

git push origin master