Skip to content

sheltondong/postcss-file

Repository files navigation

PostCSS File

PostCSS File is a assets handler for css. It can copies assets and overwrites your url, it also can inserts images as a inline data.

Installation

npm install --save-dev postcss-file

Usage

Webpack

// webpack.config.js
module.exports = {
  // ...
  module: {
    rules: [
      // ...
      {
        test: /\.css$/,
        use: [{
          loader: 'postcss-loader',
          options: {
            plugins: [
              // other plugins ...
              require('postcss-file')({
                url: 'copy',
                assetsPath: 'dist/assets',
                publicPath: './assets/',
                hash: true
              })
            ],
          },
        }]
      }
    ]
  }
}

Rollup

// rollup.config.js
import postcss from 'postcss';

const config = {
  // ...
  plugins: [
    // ...
    postcss({
      // ...
      plugins: [
        // other plugins ...
        require('postcss-file')({
          url: 'copy',
          assetsPath: 'dist/assets',
          publicPath: './assets/',
          hash: true
        })
      ]
    })
  ]
};

export default config;

Note: You must use options to specify how would you like to handle your assets in your css, if you don't pass any options, PostCSS File will do nothing about your assets. Additionally, for the full effects for your assets, please put PostCSS File plugin on the lastest of postcss plugins.

Url Resolve

You can copy your assets to anywhere or insert them as inline data through "url" option.

Copy

postcss({
  plugins: [
    require({
      url: 'copy',
      assetsPath: './dist/assets',
      publicPath: 'assets/'
    })
  ]
})

Input:

.app-body {
  background-image: url('./imgs/background.png');
}

Output:

.app-body {
  background-image: url('./assets/background.png');
}

Note: Remember that you should specify the publicPath option since we know nothing about your structure of your project directories, and also we don't know where you want to output your css file. If you don't specify the publicPath option, we would use the assetsPath option to be your url prefix, and obviously, it is normally not what you want.

Inline

postcss({
  plugins: [
    require({
      url: 'inline',
    })
  ]
})

Input:

.app-body {
  background-image: url('./imgs/background.png');
}

Output:

.app-body {
  background-image: url('data:image/png;base64,<base64>');
}

Options

option type description default
url string determines how to handle the url, "copy" or "inline". require assetsPath "inline"
assetsPath string where the assets should be copy to. undefined
publicPath string the prefix of output url undefined
extensions string[] determines which type of files should be handle all
include string[] determines where to search for assets all
exclude string[] determines which folder should be exclided none
hash boolean use hash to be the asset's name false

For example

postcss({
  plugins: [
    require({
      url: 'copy',
      assetsPath: './dist/assets',
      publicPath: './assets/',
      extensions: ['.jpg', '.png', '.gif', '.ttf', '.otf'],
      include: [
        'src'
      ],
      exclude: [
        'node_modules',
      ],
      hash: true
    })
  ]
})

See PostCSS docs for examples for your environment.

About

PostCSS plugin for handle assets

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published