Move API to use/fallback in v2

[bebraw]

To comply with use, the API should look like this (to quote @sokra):

use: ETP.extract({
  fallback: [
    { loader: "style-loader", options: {} }
  ],
  use: [
    { loader: "css-loader" },
    { loader: "postcss-loader", options: { plugin() { ... } } }
  ]
})

We probably should give deprecation messages for the old fields.

[jaydenseric]

Should it not be loader: ETP.extract({?

When did fallbackLoader get replaced with a fallback array? The readme must need updating.

Also, just want to clarify mixing objects and strings in use arrays will be ok, like with webpack.

So you could do:

loader: ETP.extract({
  fallbackLoader: 'style-loader',
  use: [
    'css-loader',
    {
      loader: 'postcss-loader',
      options: { ... }
    }
  ]
})

Or if css-loader requires options:

loader: ETP.extract({
  fallbackLoader: 'style-loader',
  use: [
    {
      loader: 'css-loader',
      options: {
        importLoaders: 1
      }
    },
    {
      loader: 'postcss-loader',
      options: { ... }
    }
  ]
})

[bebraw]

Hi,

This change hasn't been done yet. That's why the README isn't done yet.

The old loader: plugin.extract legacy syntax is still supported although use is preferred.