Builds the project for production.
npx frontity build [options]
frontity serve command will use the files generated by this
frontity build command.
Builds the project for development. Related environment variable:
Create bundles with "es5", "module" or "both". Default target is "both". Related environment variable:
Output usage information
Builds the project for production using an external domain
https://external-domain.com/static as the path for static files
npx frontity build --public-path="https://external-domain.com/static"
For example, when running react in development mode (when
process.env.NODE_ENV is set to
development and NOT to
production) you get full error messages and warnings from React but at the cost of slower performance.
npx frontity build --development
So, it’s basically the same as just running
frontity dev except that it will only build the project
once and will not run the development server.
By default Frontity will look for static assets in the path
--public-path option you can change the path from where you are serving the statics assets (i.e. js chunk files, fonts, images, etc.)
The public path is included in the generated files by webpack and cannot be changed after that.
In case some people need to change it (because of constrains in their site architecture) they would need an option to do so just before generating the Frontity bundle with
npx frontity build.
npx frontity build --public-path="/other/folder"
Create bundles with
both. Default target is
If detected, and no
--target option is defined for
build Frontity command, this environment variable will be applied.
Frontity by default builds the server in "production mode". Setting this variable makes it run in "development mode" (with disabled optimizations, etc.)
Set the public path for static assets. Default path is