# options ## --mhy-help ```bash # show usage details mhy --mhy-help ``` ## --mhy-debug ```bash # show debug messages mhy --mhy-debug ``` ## --mhy-verbose ```bash # show more info than usual mhy --mhy-verbose ``` ## --mhy-env Controls `process.env.NODE_ENV` variable and adds support to have multiple secondary environments. Aliases: * `prod`: `production` * `dev`: `development` *(default)* ### Basic Usage ```bash # Run as NODE_ENV=production mhy eslint --mhy-env=prod # Run as NODE_ENV=production with secondary env called `ci` mhy eslint --mhy-env=prod:ui ``` ### Secondary environments You can use the `:` separator to define multiple secondary environments. > The first environment will be always set as a value for `process.env.NODE_ENV`. Example ```bash # Run webpack with configuration loaded for production mode, on Travis-CI only for the master branch. mhy webpack --mhy-env=prod:travis:master ``` > Secondary environments are supported and config also. ## --mhy-if Executes the command only when the given expression is *truthy*. ```bash # On building master I don't need to run tests because they were validated before pull requests mhy jest --mhy-if="!process.env.MHY_ENVS.includes('master')" ``` ## --mhy-version ```bash # show mhy's currently installed version mhy --mhy-version ``` --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://mhy.js.org/tools/built-ins/options.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.