editor

This setting specifies which editor to open your current project in when using the command flag --edit.
Default: Sublime Text

minifyHTML

If set to true, this setting minifies your HTML in production. The settings for minification can be adjusted in the htmlminOptions-array below.
Default: false

htmlminOptions

An array with options for minifyHTML. A complete list with all available options can be found here: https://github.com/kangax/html-minifier.

combineMediaQueries

A boolean value that determines whether to combine the same media-queries across your Sass / CSS as one or not. They are sorted according to the “first-win“ algorithm a.k.a. order of appearance in your files. Keep this in mind when declaring media-queries.
Default: true

browserlist

This is no longer a setting in the latest version of Frontio. The setting has been replaced by a .browserslistrc file. More info: https://github.com/browserslist/browserslist.

This setting consists of an array of browsers for which Frontio has to provide prefixes and fallbacks. (Autoprefixer, PostCSS)

You can edit the contents of the .browserslistrc file to target CSS compatibility in specific browsers. If no .browserslistrc file is found, Frontio will use a fallback browser configuration.

Note: the fallback browsers are the same as the ones listed in the Frontio boilerplate's .browserslistrc file.

useUncss

Setting this to true will let Frontio remove all unused CSS from your files when running in production. This works only on css linked to html-files.
Default: false

uncssIgnore

This provide an array of selectors that should not be removed by UnCSS. Both literal names and regex patterns are recognized. You can also add a specific uncss comment before certain selectors in your css: /* uncss:ignore */
Default: []

hint_js

If you are learning JavaScript and want to get used to the best coding practices, set this option to true. Use the .eslintrc.json file that comes with the Frontio boilerplate or add it to the root folder of your project manually. Errors, warnings and notifications will then be logged in the command line output. Find a complete list of available rules here: https://eslint.org/docs/rules/.
Default: false

hint_html

Similar to hint_js, this setting notifies your through the command line with best practices for html coding. The rules can be adjusted in the .htmlhintrc.json file in your project's root folder.
Default: false

assetsFolder

The source path to your current project's assets folder.
Default: assets

export_assets

The destination path to where your assets (css, js, images, docs, ...) will be exported.
Default: export

export_templates

The destination path to where your templates will be exported.
Default: export

export_misc

The destination path to where your miscellaneous files (humans.txt, robots.txt, .htaccess, ...) will be exported.
Default: export

assemble_templates

This setting makes sure that all your partials and layouts are found and correctly injected into your main html files.
Default: true

template_asset_prefix

A path that should be prefixed to each injected file path.

proxy

Proxy an existing vhost. Browsersync will wrap your vhost with a proxy URL to view your site.

css_timestamp

When set to true, a timestamp like ?v=1580400496963 is appended to your included CSS path.
This is a development-only option. CSS and JS file paths are automatically suffixed with a timestamp when running Frontio in production.
Default: false

On slower internet connections, this may result in slightly slower browser reload.

js_timestamp

When set to true, a timestamp like ?v=1580400496963 is appended to your included JS path.
This is a development-only option. CSS and JS file paths are automatically suffixed with a timestamp when running Frontio in production.
Default: false

On slower internet connections, this may result in slightly slower browser reload.