Disallow webpack from using cssnext as a loader

[jasonkuhrt]

Basically this should never happen webpack/webpack#725 (comment)!

[MoOx]

Note sure we can handle in cssnext, since webpack probably try module as a simple function (cssnext is such a function, that take a string as first param).
This should be handled in webpack probably...

[MoOx]

I am open to do something, but what?... I've no idea.

[jasonkuhrt]

This should be handled in webpack probably...

@sokra agree?

[sokra]

I can imaging no non-breaking webpack change which would fix this, but I schedule a breaking change for 2.0...

You can add this to cssnexts package.json:

  "loader": "this is not a loader"

[MoOx]

Maybe more something like

  "webpack": {
    "loader": "cssnext-loader" // then this warn user about using the appropriate loader
  }

[jasonkuhrt]

Hurray for untyped languages. CC @stresslimit

[sokra]

@MoOx This is supported, but it's only "loader": "cssnext-loader"

[MoOx]

adding a "loader" key in a package.json with the name of the real loader to use warn the user ? That would solve the issue then... What did I miss ?

[MoOx]

@sokra do you confirm that adding "loader": "cssnext-loader" in package.json in cssnext package will make webpack look for cssnext-loader and throw an error if this package is missing?

[sokra]

Actually I think "loader": "cssnext-loader" is like "loader": "./cssnext-loader" and try to resolve to a file in the package. It works like the "main" field.

[MoOx]

Nobody has got the same issue, so I am closing.

[MoOx]

Someone just get the same issue, I will make something to avoid this again.

[bloodyowl]

how about a npm_loader field, @sokra ?

[iam4x]

Great job @MoOx thank's 👍