Load the .env that was declared, and read brackets as a flag

azer commented

2026-09-16 08:20:06 +00:00

Owner

Two things about configuration here. dotenv has been a dependency since the first commit and is never imported, so a .env file sits there doing nothing and only a shell export ever reaches the process. And everything in process.env is a string, so 'process.env.brackets || false' turned brackets ON for brackets=false exactly as readily as for brackets=true - a non-empty string is truthy. Measured before and after: with brackets=false set, 25 of 25 generated tasks came back containing brackets; after the change, 0 of 25, and brackets=true still gives 25 of 25. A .env placed next to index.js now takes effect, and .gitignore is added so it does not get committed.

azer added 1 commit

2026-09-16 08:20:06 +00:00

Load the .env that was declared, and read brackets as a flag 76688feafb

dotenv has been a dependency since the first commit and was never imported, so
a .env sat there doing nothing and only a shell export reached the process.

And every value in process.env is a string: 'process.env.brackets || false'
turned brackets on for brackets=false exactly as readily as for brackets=true,
because a non-empty string is truthy. 25 of 25 tasks came back bracketed with
brackets=false set; 0 of 25 after.

azer merged commit f7d6fa241c into master

2026-09-16 15:39:41 +00:00

azer referenced this pull request from a commit

2026-09-16 15:39:42 +00:00

Merge pull request 'Load the .env that was declared, and read brackets as a flag' (#1) from azer/env-flags into master

Rows
Columns

Load the .env that was declared, and read brackets as a flag #1