Breakpoint can be disabled or attached with some condition. There is no way to control debugger;. To me it has some value only in case if you have access to source code but browser executes minified code(without source maps) so it's really hard to find appropriate line to put breakpoint.
The discussion was about whether or not to use console.log (where you need to be working with source code anyway) so debugger is a useful alternative in this case. For a production build, it would be common practice to minify and uglify the code - stripping out all console logging and 'debugger' statements. So, in that regard, yes, you are correct - this would not apply to a production build scenario.
Obviously, your tools and approaches will vary according to the situation. It's helpful to be aware of all approaches and use as you see fit.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.