In order to fit your development environment's needs, Clarion is configurable. If the default configuration is used, no config file is generated in order to avoid unnecessary clutter in your project. To add a config file to your project, run the following command at the root of your project:

clarion config init

You should now see a new file called .clarion in your project. The file contains a simple JSON object.

    "paths": {
        "styles": "./src",
        "scripts": "./src"
    "format": {
        "styles": "scss",
        "scripts": "js"
    "addToManifest": "true",
    "importAbstracts": "true"

You can modify this content directly using your text editor, but you can also use the Clarion CLI to make changes.


You can change the location of your project contents. This is extremely useful if you are using a framework or have a specific architecture you need to adhere to.

For example, if I wanted to move my styles folder to a directory called "app" rather than "src" I could do so using the following command (Note: Clarion will look for your styles in directories called sass, scss, or less):

clarion config paths.styles app


You can change the file format. This will not change the existing files, but will take effect for new files.

clarion config format.styles less

Any new files will now use the .less style format.

Add To Manifest

If you would like to turn off the feature of automatically adding an import statement for new files to your manifest file, you can turn it off using the following command:

clarion config addToManifest false

You can turn it back on again by setting the value to true.

Import Abstracts

When a new style file is created, the Abstracts manifest file is imported to give you access to your variables, mixins, etc. Some developers may want to be more selective about the files they would like to import. You can prevent Clarion from adding this reference using the following command:

clarion config importAbstracts false

You can turn it back on again by setting the value to true.