You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I have a command that ends up running out of memory, it should return code 134 (on Unix, at least). But instead, when used with dotenv-cli, the code is 0. This creates issues in CI environments. For example, a test suite that runs out of memory counts as passing.
To reproduce, create a file test.js with these contents:
If I have a command that ends up running out of memory, it should return code 134 (on Unix, at least). But instead, when used with
dotenv-cli
, the code is 0. This creates issues in CI environments. For example, a test suite that runs out of memory counts as passing.To reproduce, create a file
test.js
with these contents:And then run this in your terminal:
The text was updated successfully, but these errors were encountered: