Update peer dependency of stylelint to version 7.1.0 (latest release).

I'm happy to look into a pull request for this.

When I try to use stylelint-loader I get the following error on every css file:

Module build failed: Error: You must use a valid syntax option, either: scss, less or sugarss

Here's my webpack config:

module: {
  preloaders: [
    {
      test: /\.css$/,
      loader: 'stylelint',
      include: srcPath,
    },
  ],
  loaders: [
    {
      test: /\.css$/,
      include: srcPath,
      loader: 'style!css!postcss'
    },

    ...
  ],
},
stylelint: {
  configFile: path.join(__dirname, relativePath, '.stylelintrc'),
},

My .stylelintrc:

{
  "extends": "stylelint-config-standard"
}

Using the CLI everything works fine.

Here some information about the package versions I have:

node: 6.3.1
stylelint: 7.1.0,
stylelint-loader: 6.1.0,
webpack: 1.13.1

Please let me know if you need any additional information.

Hi,
Tell me please why I get error when I run webpack with style-loader?:
ERROR in Cannot find module 'chalk'

Node: v4.4.2
NPM: 2.15.3
OS: Windows 10

Currently the loader will emit warnings about the configFile missing even if it hasn't been specified. As styleloader will happily figure out the correct configFile by itself (or fall back to the package.json config) this seems redundant.

A workaround is explicitly adding stylelint: {configFile: false} to the webpack config to avoid the loader's warnings.

There is an issue where errors reported by files imported by other sass files are not bubbled up correctly. Need to see what is going on, design a unit test and then fix the test.

npm install --save-dev stylelint will currently install [email protected] which causes stylelint-loader to give an EPEERINVALID

Hi @adrianhall, does this plugin recursively lint imported files (Sass or otherwise) such as @import sub-module/sub-module? If not, would it be possible to have it do so?

I'm seeing the ERROR in Cannot find module 'chalk' when using this loader.

I believe that the issue is that chalk is not defined as a dependency of this module. This wasn't an issue for me running under npm v3 as it has has flat module dependencies and chalk is a dependency of stylelint. I picked up the issue when running webpack using npm v2. Chalk is not available to stylelint-loader when using npm v2 and this causes the above error

Set up a hot reloader config with stylelint in the preLoaders. Configure another preloader for eslint.

When the reloader rebuilds the package, note that eslint is run, but stylelint is not.

Hi,
Could you please explain what is the point to cache files in stylelint loader?
In the current implementations linter checks each file only once.

Let's take an example. One of project style files has lint error:

1. User runs webpack dev server.
2. User sees stylelint error.
3. User does some changes on the same file, but doesn't fix the problem.
4. Webpack re-rebundles files.
5. User doesn't see the error anymore.
6. However the lint error still exist.

Looks like a bug for me.

P. S. Temporary workaround to add ignoreCache: true to webpack config file.

This could be something I've done wrong.

I was following this tutorial (https://shellmonger.com/2016/01/29/integrating-sass-lint-with-webpack/comment-page-1/) to figure out how to add stylelint to Webpack.

I’m running Eslint for my js which is working fine. But for some reason nothing happens with my scss no matter how badly I break the rules I set.

I’m using the following in my webpack config (Full config file here: http://codepen.io/davislurve/pen/gPdxzB):

stylelint: {
    configFile: path.join(__dirname, ‘./.stylelint.config.js’),
    rules: {
        ‘function-url-quotes’: ‘single’,
        ‘indentation’: [ 4, { warn: true } ],
        ‘string-quotes’: ‘single’
    }
}

but when I use double quotes or 2 space indentation in my SCSS code nothing appears in the console.

It also doesn’t throw an error if I change the config file name e.g:

configFile: path.join(__dirname, ‘./SOME_RANDOM_FILE.config.js’),

I was expecting an error saying the file can’t be found or something. So I’m wondering if it’s even being initiated properly.