Instead of defining my own DEBUG variable, use WP_DEBUG

[siamkreative]

In public/assets/js/betterOptin-config.js, I should be using a variable called wpDebug instead, that is true when WP_DEBUG is enabled. Therefore, the console.log() would automatically trigger.

[siamkreative]

Actually, I think it should work that way:

• If WP_DEBUG is enabled, then load the source JavaScript (unminified), that contains console.log() statements
• If WP_DEBUG is disabled, then load the dist JavaScript file (minified), and remove the console.log() statements programmatically.

Remove console.log() programmatically

https://github.com/ehynds/grunt-remove-logging https://www.npmjs.com/package/grunt-contrib-uglify#conditional-compilation

[siamkreative]

We're already using gulp-strip-debug here https://github.com/ThemeAvenue/BetterOptin/blob/master/gulpfile.js#L81

[siamkreative]

8c268ea35be4ba291edbdab8d7083834428e6e89