Skip to content
This repository was archived by the owner on May 1, 2020. It is now read-only.

Commit 3080139

Browse files
leifwellsdanbucholtz
authored andcommitted
chore(readme): correct content on dev vs prod build
* Update ReadMe.md, updating prod/dev build info * Update README.md
1 parent eabd125 commit 3080139

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -156,7 +156,7 @@ These environment variables are automatically set to [Node's `process.env`](http
156156

157157

158158

159-
The `process.env.IONIC_ENV` environment variable can be used to test whether it is a `prod` or `dev` build, which automatically gets set by any command. By default the `build` task is `prod`, and the `watch` and `serve` tasks are `dev`. Additionally, using the `--dev` command line flag will force the build to use `dev`.
159+
The `process.env.IONIC_ENV` environment variable can be used to test whether it is a `prod` or `dev` build, which automatically gets set by any command. By default the `build` and `serve` tasks produce `dev` builds (a build that does not include Ahead of Time (AoT) compilation or minification). To force a `prod` build you should use the `--prod` command line flag.
160160

161161
Please take a look at the bottom of the [default Rollup config file](https://github.com/driftyco/ionic-app-scripts/blob/master/config/rollup.config.js) to see how the `IONIC_ENV` environment variable is being used to conditionally change config values for production builds.
162162

0 commit comments

Comments
 (0)