Disable sourcemap (CSS) generation in production environment

[ivanionut]

modifies the SassProcessor to set sourcemap_filename to None in production environments. This optimization reduces file size, improves performance, and eliminates unnecessary debug information in production builds. Sourcemaps remain fully functional in development mode.

[jrief]

There should be an explicit Django settings named SASS_PROCESSOR_CREATE_SOURCEMAP, it can default to the same value as DEBUG but users must have the possibility to override it.

Documentation is missing.

Tests are missing.

[ivanionut]

hi @jrief
I thought it was an oversight, for two reasons:

1. documentation already exists with:

During development, a sourcemap is generated along side with the compiled *.css file. This allows to debug style sheet errors much easier.

2. similar logic already exists in the code:

django-sass-processor/sass_processor/processor.py

Lines 97 to 98 in 0d8cb67

	if not settings.DEBUG:
	options.append('--no-map')

[jrief]

Well, then why did you create a pull request?

In production, CSS files are pregenerated anyway using ./manage.py compilescss and by specifying that option, sourcemaps are not generated.

In development CSS files und sourcemaps are generated on the fly. Does it really make sense to disable sourcemaps during development?

[ivanionut]

In production, CSS files are pregenerated anyway using ./manage.py compilescss and by specifying that option, sourcemaps are not generated.

Using ./manage.py compilescss correctly compiles CSS files without the sourcemap.
But if I DON'T use the compilescss command and set DEBUG=False and SASS_PROCESSOR_ENABLED=True, then the CSS files are generated WITH the sourcemap. This should be considered incorrect behavior.

In development CSS files und sourcemaps are generated on the fly. Does it really make sense to disable sourcemaps during development?

No, absolutely not. I don't need to change the behavior in the development environment.

[jrief]

If I understand you correctly, in production you want to generate the CSS files on the fly and then serve them through the Django's staticfiles app? This means that every time a CSS file is loaded, Django has to iterate over all static-folders from all apps and look for the proper file. Maybe I misunderstood your intention, but if you try to do what I just wrote, I would say that this is a big no-no.

[ivanionut]

Even now, if you set DEBUG=False and SASS_PROCESSOR_ENABLED=True, SCSS files are compiled on the fly in production.

[jrief]

Even now, if you set DEBUG=False and SASS_PROCESSOR_ENABLED=True, SCSS files are compiled on the fly in production.

I would strongly recommend against such a setting.