Looking For Anything Specific?

Protect Your Source code from public access - its easy just follow simple steps.

how to share source code securely,source code protection best practices,source code theft,dlp source code protection,github protect source code,secure source code repository,

Source code and map

how to share source code securely,source code protection best practices,source code theft,dlp source code protection,github protect source code,secure source code repository,

 
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.

Your Source Is Public

how to share source code securely,source code protection best practices,source code theft,dlp source code protection,github protect source code,secure source code repository,
 
When a web is published, then you only publish the build folder. Now from the previous section, we know that the map file is only needed to debug. If we publish the build folder with the map files, then your source code is considered.

Where to find source code
  • Inspect the web page from a browser.
  • Go to the Source tab.
  • There you will find the whole path of the source.

Solution

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.