Webpacker: Remove Post CSS

Created on 30 Aug 2018  路  4Comments  路  Source: rails/webpacker

How can I remove PostCSS? My app does not require it but it's causing errors due to my use of CSS Custom Properties.

Thanks

style loaders support

Most helpful comment

for the interwebs wonderer, you can nuke built in configs with :

environment.loaders.delete('sass')
environment.loaders.delete('moduleSass')
environment.loaders.delete('moduleCss')
environment.loaders.delete('css') // this is the problematic one usually ! 

show some <3

All 4 comments

Any ideas? I really need to remove it but am unsure how to do so.

A quick and dirty way to do this would be the following in config/webpacker/environment.js

environment.loaders.forEach(element => {
  environment.loaders.get(element.key).use = environment.loaders.get(element.key).use.filter(rule => rule.loader !== 'postcss-loader')
});
let keys = ['css', 'sass', 'moduleCss','moduleSass']

keys.map(function(key) {
  let thing = environment.loaders.get(key)
  let index = environment.loaders.get(key).use.findIndex(el => el.loader === 'postcss-loader');

  thing.use[index].options = {
    plugins: (loader) => [
      require('postcss-cssnext')({
        features: {
          customProperties: {
            warnings: false
          }
        }
      })
    ],
    modules: true,
    sourceMap: true,
    localIdentName: '[name]__[local]___[hash:base64:5]',
  }

})

Another dirty solution that I came up with for turning off the warnings, since I use bulma.

for the interwebs wonderer, you can nuke built in configs with :

environment.loaders.delete('sass')
environment.loaders.delete('moduleSass')
environment.loaders.delete('moduleCss')
environment.loaders.delete('css') // this is the problematic one usually ! 

show some <3

Was this page helpful?
0 / 5 - 0 ratings

Related issues

swrobel picture swrobel  路  3Comments

amandapouget picture amandapouget  路  3Comments

naps62 picture naps62  路  3Comments

itay-grudev picture itay-grudev  路  3Comments

ilrock picture ilrock  路  3Comments