https://github.com/zenflow/node-bug-windows-process-dot-env
Reproduction repo for a bug in NodeJS
https://github.com/zenflow/node-bug-windows-process-dot-env
Last synced: about 1 year ago
JSON representation
Reproduction repo for a bug in NodeJS
- Host: GitHub
- URL: https://github.com/zenflow/node-bug-windows-process-dot-env
- Owner: zenflow
- Created: 2018-02-26T11:53:06.000Z (over 8 years ago)
- Default Branch: master
- Last Pushed: 2018-02-27T21:57:48.000Z (over 8 years ago)
- Last Synced: 2025-02-13T15:54:59.730Z (over 1 year ago)
- Language: JavaScript
- Size: 3.91 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# node-bug-windows-process-dot-env
Reproduction repo for a bug in NodeJS
## Status
| Operating System | CI Service | Status |
| --- | --- | --- |
| Linux | Travis | [](https://travis-ci.org/zenflow/node-bug-windows-process-dot-env) |
| Windows | AppVeyor | [](https://ci.appveyor.com/project/zenflow/node-bug-windows-process-dot-env) |
## Description
After being assigned the value of `''`, the value of `process.env.foo` can sometimes be observed to be `undefined`.
This seems to only happen in Windows environments.
It also happens rather unpredictibly (yet consistently). There are two tests in the tests dir: `symptom.js` and `no-symptom.js`. `symptom.js` will show the symptom on Windows and `no-symptom.js` will not. But look how similar the two tests are, and how the difference would not be expected to change the outcome.
## Links
- [`symptom.js`](./tests/symptom.js)
- [`no-symptom.js`](./tests/no-symptom.js)
- [Travis Build Logs](https://travis-ci.org/zenflow/node-bug-windows-process-dot-env)
- [AppVeyor Build Logs](https://ci.appveyor.com/project/zenflow/node-bug-windows-process-dot-env/branch/master)