mirror of
https://github.com/kremalicious/metamask-extension.git
synced 2024-11-22 09:57:02 +01:00
b124ac29fc
Our build script waits for the `close` event to determine whether the task has exited. The `exit` event is a better representation of this, because if a stream is shared between multiple processes, the process may exit without the `close` event being emitted. We aren't sharing streams between processes, so this edge case doesn't apply to us. This just seemed like a more suitable event to listen to, since we care about the process exiting not the stream ending. See this description of the `close` event from the Node.js documentation [1]: >The `'close'` event is emitted when the stdio streams of a child >process have been closed. This is distinct from the `'exit'` event, >since multiple processes might share the same stdio streams. And see this description of the `exit` event: >The `'exit'` event is emitted after the child process ends. [1]: https://nodejs.org/docs/latest-v14.x/api/child_process.html#child_process_event_exit |
||
|---|---|---|
| .. | ||
| build | ||
| lib | ||
| announcer.js | ||
| auto-changelog.sh | ||
| chromereload.js | ||
| create-static-server.js | ||
| empty.js | ||
| generate-migration.sh | ||
| gource-viz.sh | ||
| metamaskbot-build-announce.js | ||
| missing-locale-strings.js | ||
| mock-3box.js | ||
| mock-segment.js | ||
| README.md | ||
| require-react-devtools.js | ||
| run-ganache.sh | ||
| sentry-publish.js | ||
| sentry-upload-artifacts.sh | ||
| shellcheck.sh | ||
| show-deps-install-scripts.js | ||
| source-map-explorer.sh | ||
| sourcemap-validator.js | ||
| static-server.js | ||
| verify-locale-strings.js | ||
Development
Several files which are needed for developing on(!) MetaMask.
Usually each files contains information about its scope / usage.