Unknown word (CssSyntaxError)stylelint(CssSyntaxError)

[bikashd003]

a new issue occurs on every code file, whether it is simple boilerplate code or complex code, the issue is
"Unknown word (CssSyntaxError)stylelint(CssSyntaxError)"

[hex-ci]

Thank you for your feedback. In version 0.57, I upgraded the internal stylelint version to 15 in the extension and made it compatible with 16, so there may be some differences. I suggest you use the useLocal option, using the stylelint in your project. If you don't want to use the useLocal option, you can exclude these erroneous files in your stylelint configuration file.

[BohdanYavorskyi]

@hex-ci it just doesn't make any sense. All jsx, tsx files are scanned (not styles) and error. Please take a look at what can break it and try to fix. Thanks in advance.

[hex-ci]

@hex-ci it just doesn't make any sense. All jsx, tsx files are scanned (not styles) and error. Please take a look at what can break it and try to fix. Thanks in advance.

Please use useLocal option.

[BohdanYavorskyi]

@hex-ci it just doesn't make any sense. All jsx, tsx files are scanned (not styles) and error. Please take a look at what can break it and try to fix. Thanks in advance.

Please use useLocal option.

if I don't have local configuration. Where this one should be added?

[hex-ci]

@hex-ci it just doesn't make any sense. All jsx, tsx files are scanned (not styles) and error. Please take a look at what can break it and try to fix. Thanks in advance.

Please use useLocal option.

if I don't have local configuration. Where this one should be added?

The reason for these problems is that I upgraded the version of stylelint inside the extension. Normally, you should use the stylelint in node_modules in the project, and it is best not to use the stylelint inside the extension. Because the extension can only have a fixed version of stylelint built-in, it may not be suitable for everyone.

If I were to go without any local stylelint, then I would have to downgrade the stylelint inside the extension, but stylelint 16 and later versions will become increasingly incompatible and the problem will never go away.

Therefore, the best solution is to use local stylelint.

[hex-ci]

You can't use very old stylelint forever, which is also bad for development.

[hex-ci]

In addition, you can also exclude files that do not require lint by configuring the ignoreFiles option of stylelint.config.js, for example: ignoreFiles: ['**/*.{js,cjs,mjs,ts,tsx,svg,md}' , 'dist/**', '.*', 'node_modules/.*/**']

For files such as vue and html, you may also need a configuration similar to this in the stylelint.config.js file:

overrides: [
  {
    files: ['**/*.{vue,html}'],
    customSyntax: 'postcss-html',
  },
],

You need to install postcss-html via npm.

[hex-ci]

@hex-ci it just doesn't make any sense. All jsx, tsx files are scanned (not styles) and error. Please take a look at what can break it and try to fix. Thanks in advance.

Please use useLocal option.

if I don't have local configuration. Where this one should be added?

In fact, the usage is similar to eslint. If you have not initialized a project through npm init, then you should initialize a project first. If the project already exists, then you should npm i -D stylelint to install a stylelint, and then just like a normal front-end project Just use stylelint. If useLocal is true, the stylelint installed in your project will be used.

[vinit-poojary]

I'm getting the same error for both TS and TSX files. Should I ignore them?

[hex-ci]

I'm getting the same error for both TS and TSX files. Should I ignore them?

yes，ignore them. OR use useLocal option, then install stylelint v13

[time4nothing]

I am also having this problem since updating to stylelint-plus v0.57.0. Problem goes away if I install the previous version v0.56.6. Will this bug be fixed soon?

[sanket95droid]

not able to downgrade to stylelint v13 please help?

[hex-ci]

not able to downgrade to stylelint v13 please help?

Downgrading is not a good idea. Because the latest version of stylelint is now v16, v17 may come soon. We can't always use a very old version of stylelint. If you want to use an old version of stylelint, please turn on the useLocal option to use stylelint in your own project directory.

[hex-ci]

I am also having this problem since updating to stylelint-plus v0.57.0. Problem goes away if I install the previous version v0.56.6. Will this bug be fixed soon?

Downgrading is not a good idea. Because the latest version of stylelint is now v16, v17 may come soon. We can't always use a very old version of stylelint. If you want to use an old version of stylelint, please turn on the useLocal option to use stylelint in your own project directory.

[sanket95droid]

I am also having this problem since updating to stylelint-plus v0.57.0. Problem goes away if I install the previous version v0.56.6. Will this bug be fixed soon?

Downgrading is not a good idea. Because the latest version of stylelint is now v16, v17 may come soon. We can't always use a very old version of stylelint. If you want to use an old version of stylelint, please turn on the useLocal option to use stylelint in your own project directory.

what actually is useLocal and where to use it, can you provide reference to any docs? I found it in stylelint-plus..
Thank you

[hex-ci]

I am also having this problem since updating to stylelint-plus v0.57.0. Problem goes away if I install the previous version v0.56.6. Will this bug be fixed soon?

Downgrading is not a good idea. Because the latest version of stylelint is now v16, v17 may come soon. We can't always use a very old version of stylelint. If you want to use an old version of stylelint, please turn on the useLocal option to use stylelint in your own project directory.

what actually is useLocal and where to use it, can you provide reference to any docs? I found it in stylelint-plus.. Thank you

Install stylelint v13 in your project root directory: npm i -D stylelint@13, then the useLocal option will take effect, which should have the same effect as the old version of stylelint-plus extension.

[le0nik]

I have stylelint@14 and useLocal is enabled and I'm still getting this error.

[hex-ci]

I have stylelint@14 and useLocal is enabled and I'm still getting this error.

You must use stylelint v13, or use v14 or higher and add the ignore configuration, because stylelint v14 and higher does this.