Should I add sourcemaps to the finished site?

Question

Web development

Hello. I asked a question

earlier in order to facilitate the work of myself and other developers who will work with the site in the future. The answer was to add sourcemaps to the project. Via gulp for the min.js and min.css files I implemented this. I also left license information with versions in these files, so that it is clear where which library begins and ends. Now I read that you do not need to upload the site along with sourcemaps, but with it it is much easier to understand what kind of libraries are installed otherwise where to store it then, on a local server. So how to do it right and in general are there any other ways to display installed libraries on the site in the form of a list?

Answer 1

Now I read that you do not need to upload the site along with sourcemaps, but with it it is much easier to understand what kind of libraries are installed otherwise where to store it then, on a local server.

In production, there should be only the final code, and nothing more. No assemblers, packages, maps and the like. If you have some kind of working guideline, and you are not the only developer on the project, then you have a dev branch in git. From where your colleagues can clone the entire toolkit - through the same package.json

Answer 2

You don't need to add sortsmaps for production. But they must be generated and uploaded to the sentry so that the fall of the front can be analyzed.

Answer 3

Sourcemaps are needed to debug your code. For girls and stage environments, they are worth using. You shouldn't do this in production.