process.env.DEBUG not working?

First, I’m not reopening your recent debate on inline changes to process.env. I support the ability to do so, it just that it doesn’t seem to be working for us anymore.

There are specific cases where the ONLY way to set things is via inline code setting those vars. For us, this is Lambda@Edge which do NOT support env vars as regular functions do.

So for us, this is the only way. The top of our functions look something like this… index.js

process.env.DEBUG = 'logger:*';

const AWS = require('aws-sdk');
const Promise = require('bluebird');
const crypto = require('crypto');
const _ = require('lodash');
const logger = require('../_common/utils/logger');
...

/_common/utils/logger

const debug = require('debug');
const log = debug('logger:logs');
log.log = console.log.bind(console);

module.exports = log;

Note: We are using webpack to bundle our lambda functions (Edge Functions need to be tiny). Not sure if that has anything to do with why it would not work.

This was working previously, and now seems to have stopped working. What are we doing wrong?

[iDVB]

Nm, turns out there is another issue at play unrelated to Debug which may be causing this. I’ll give an update once we sort it out.

Thanks!

On Wed, Dec 8, 2021 at 9:40 AM Qix @.***> wrote:

Without seeing code (and since I don’t use lambdas) it’s really hard to debug. The best advice without more debugging information is what I mentioned before - the assignment needs to come before debug is ever initialized.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/debug-js/debug/issues/815#issuecomment-988872067, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABOIQQOXXBT6FANWINXTADUP5U4HANCNFSM4YLIWS4A .

[Qix-]

Without seeing code (and since I don’t use lambdas) it’s really hard to debug. The best advice without more debugging information is what I mentioned before - the assignment needs to come before debug is ever initialized.