Copilot keeps suggesting `console.log` in production code. How to train it not to?

I've seen this happen in code reviews. Copilot is trained on public repos, and let's be honest, a huge percentage of those are littered with `console.log` statements. It's picking up a bad habit from the community.

You can't directly "train" Copilot, but you can steer its suggestions. Here are the most effective methods:

* **Use a dedicated development configuration file.** Create a `.env.development` or similar and conditionally log based on the environment. Copilot will start to pick up this pattern.
```javascript
// In your environment config
const isDevelopment = process.env.NODE_ENV === 'development';

// A wrapper function it can learn
export const devLog = (...args) => {
if (isDevelopment) {
console.log('[DEV]', ...args);
}
};
```
* **Adopt a proper logging library.** Start typing `logger.` and let Copilot suggest `logger.info`, `logger.debug`. It will associate logging with that object.
* **Write explicit comments.** Before the line where you need output, type a comment like `// Use the configured logger here` or `// Validate the response without console.log`. This guides the next-line suggestion.
* **Reject the bad suggestions consistently.** When it suggests `console.log`, immediately reject it (Ctrl+Enter, then select a different suggestion or just keep typing). Over time, your local model *might* adapt slightly.

The root problem is architectural. If you're in a Node.js environment, every stray `console.log` is a synchronous I/O operation. In a high-throughput production service, that's wasted compute time and a potential bottleneck. You're paying for that latency.

What's your stack? The fix differs for a React frontend vs. a Lambda function. For serverless, those logs directly impact your CloudWatch costs.