Ember CLI Postcss

Installation

1ember install ember-cli-postcss

Compatibility

Due to changes in the plugin API of Postcss V8 some plugins will need to be updated after upgrading Postcss. This should be as simple as updating this package from v6 to v7, however compatibility is not guaranteed.

• V7 ember-cli-postcss -> Postcss V8
• V6 ember-cli-postcss -> Postcss V7

Usage

The add-on can be used in two ways:

• on individual files, referred to as “compile”
• on all CSS files, referred to as “filter”

Note: it’s possible to use both compile and filter.

Additional Note: this app is compatible with Glimmer JS

Compile

This step will look for either app.css or <project-name>.css in your styles directory. Additional files to be processed can be defined in the output paths configuration object for your application:

1const app = new EmberApp(defaults, {
2  outputPaths: {
3    app: {
4      html: 'index.html',
5      css: {
6        'app': '/assets/app.css',
7        'print': '/assets/print.css'
8      }
9    }
10  }
11}

Filter

This step will run at the end of the build process on all CSS files, including the merged vendor.css file and any CSS imported into the Broccoli tree by add-ons.

Files can be white-listed and/or black-listed by using the respective include and exclude options. Each accepts an array of file globs, which are then passed on to Broccoli Funnel. An example can be seen in the sample configuration below.

Configuring Plug-ins

There are two steps to setting up postcss with ember-cli-postcss:

1. install and require the node modules for any plug-ins
2. provide the node module and plug-in options as a postcssOptions object in ember-cli-build.js

The postcssOptions object should have a “compile” and/or “filter” property, which will have the properties enabled and plugins, which is an array of objects that contain a module property and an options property:

Browser Targets

Some postcss plug-ins, like autoprefixer, allow you to configure which browsers to target for transpilation. When using Ember CLI >= 2.13.0, the browser targets configuration found in the file config/targets.js will be added to each plug-in’s options (as options.browsers). This browser list can be overwritten on a plug-in by plug-in basis. You can learn more about the targets feature on the Ember.js blog.

1postcssOptions: {
2  compile: {
3    enabled: true, // defaults to true
4    browsers: ['last 3 versions'], // this will override config found in config/targets.js
5    plugins: [
6      {
7        module: <module>,
8        options: {
9          ...
10        }
11      }
12    ]
13  },
14  filter: {
15    enabled: true, // defaults to false
16    map: false, // defaults to inline, false in production
17    browsers: ['last 3 versions'], // this will override config found in config/targets.js
18    include: ['styles/*.css'],
19    exclude: ['vendor/bootstrap/**/*'],
20    processTrees: ['css'],
21    plugins: [
22      {
23        module: <module>,
24        options: {
25          ...
26        }
27      }
28    ]
29  }
30}

Process Trees

When using the filter version of this add-on the default configuration is now to only run on the css tree. This will mean that the add-on is only run when CSS files are changed. If you need the process to run on other trees or when other files are changed, you should update the processTrees option to include more trees from the following list: [template, js, css, test, all,]

Example

Install the autoprefixer plug-in:

1npm i --save-dev autoprefixer

Specify some plug-ins in your ember-cli-build.js:

1const EmberApp = require('ember-cli/lib/broccoli/ember-app');
2const autoprefixer = require('autoprefixer');
3
4module.exports = function (defaults) {
5  const app = new EmberApp(defaults, {
6    postcssOptions: {
7      compile: {
8        enabled: false,
9      },
10      filter: {
11        enabled: true,
12        plugins: [
13          {
14            module: autoprefixer,
15            options: {
16              browsers: ['last 2 versions'] // this will override the config, but just for this plugin
17            }
18          }
19        ]
20      }
21    }
22  });
23  return app.toTree();
24};

Compile Caching

When using the compile method, the default list of file extensions for caching is set to .css, .scss, .sass, .less for faster incremental builds. If you are using a parser or filetype not in the list you will want to add the file extension as a regex to the cacheInclude option.

If you are using something like Tailwind or a postcss plugin with a JS config file that you would like to trigger a rebuild, you will need to update the options to cache JS files: cacheInclude: [/.*\.(css|scss|sass|less|js)$/], or more specifically cacheInclude: [/.*\.(css|scss)$/, /.tailwind\.js$/].

If you are using something like PurgeCSS and would like postcss to rebuild when template files are updated, you will need to update the options to cache HBS files: cacheInclude: [/.*\.(css|scss|sass|less|hbs)$/],. However, in most cases PurgeCSS should only be run for a production build and this shouldn't be necessary.

Example

1postcssOptions: {
2  compile: {
3    enabled: true,
4    cacheExclude: [],
5    cacheInclude: [/.*\.(css|scss|sass|less)$/]
6  }
7}

Developing Addons

If you are developing an addon and would like to use ember-cli-postcss to process the CSS to automatically be included in the vendor.css of Ember applications consuming the addon, there are 3 steps to follow.

1. create your styles in addon/styles/addon.css (you can import other CSS files if a postcss import plugin is installed)
2. Add a "before" option under ember-addon key in package.json

// package.json
  ...
  "ember-addon": {
    "before": [
      "ember-cli-postcss"
    ],
    "configPath": "tests/dummy/config"
  },
  ...

3. configure your addon’s options to process postcss:

1// index.js
2const CssImport = require('postcss-import')
3const PresetEnv = require('postcss-preset-env');
4
5module.exports = {
6  name: require('./package').name,
7  included: function(app) {
8    this._super.included.apply(this, arguments);
9    app.options = app.options || {};
10    app.options.postcssOptions = {
11      compile: {
12        enabled: true,
13        plugins: [
14          { module: CssImport },
15          {
16            module: PresetEnv,
17            options: { stage: 3 }
18          }
19        ]
20      }
21    }
22  },
23  ...
24};

Migrating from other Processors

If you’d like to migrate a project from one of the other processors, such as Less, Sass, or Stylus, you can configure Postcss with an appropriate parser and set of plugins that provides an equivalent set of features.

This then allows you to use additional Postcss plugins at the end of the compilation to continue transforming your styles for more powerful control of authoring styles in your application. This also plays nicely with ember-component-css.

So far this migration process has been tested when switching from Sass.

Switching from Sass

One common use case is to transition from using Sass to Postcss or using them both together. As of ember-cli-postcss@3.7.0 this is possible with the right combination of options and plugins.

There are three key pieces of configuration:

1. Set the parser to postcss-scss
2. Configure the extension to match your files (ie. 'scss')
3. Use @csstools/postcss-sass as the first plugin

Your configuration options in ember-cli-build.js would contain the following options for this addon:

1  postcssOptions: {
2    compile: {
3      extension: 'scss',
4      enabled: true,
5      parser: require('postcss-scss'),
6      plugins: [
7        {
8          module: require('@csstools/postcss-sass'),
9          options: {
10            includePaths: [
11              'node_modules/tachyons-sass',
12            ],
13          },
14        },
15        ...
16      ],
17    },
18    ...
19  }

This allows your to switch your CSS processing pipeline to use postcss without being hugely disruptive as you can keep the Sass features and .scss or .sass file extension. The importing feature of @csstools/postcss-sass will also look for .css files, so you can choose to gradually rename your files from Sass partials _<filename>.scss to <filename>.css without breaking anything.

If your goal is to completely move away from using Sass features you can remove the parser, remove the sass plugin, use an import plugin that fits your needs and ensure that your files have the .css extension.

Experimental Features

Custom Properties Service

CSS variables are now supported by many major browsers. The values of these variables can be accessed, set, and removed using JavaScript. This addon now exports a service, which provides methods to work with CSS variables. Each method is a wrapper around the browser API, which includes a check for browser support before executing.

The service provides 3 methods:

1. getVal ({ element = docEl, variableName })
2. setVal ({ element = docEl, variableName, variableValue })
3. removeVal ({ element = docEl, variableName })

A Contrived Example:

1import { inject } from '@ember/service'
2
3export default <ember object>.extend({
4  customProperties: inject(),
5  ...
6
7  nightMode() {
8    this.get('customProperties').setVal({variableName: '--background', variableValue: 'black'})
9    this.get('customProperties').setVal({variableName: '--text', variableValue: 'white'})
10  },
11
12  dayMode() {
13    this.get('customProperties').setVal({variableName: '--background', variableValue: 'white'})
14    this.get('customProperties').setVal({variableName: '--text', variableValue: 'black'})
15  },
16})

Note: if you are using postcss-custom-properties, ensure you configure the option { preserve: true }