Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Rule no-vendor-prefixes could not be found #1279

Open
Madhust opened this issue Apr 26, 2019 · 8 comments
Open

Error: Rule no-vendor-prefixes could not be found #1279

Madhust opened this issue Apr 26, 2019 · 8 comments

Comments

@Madhust
Copy link

Madhust commented Apr 26, 2019

What version of Sass Lint are you using?

v1.13.1

What did you do? Please include the actual source code causing the issue.

I can see that no-vendor-prefix file is not found in the source section of above specified version.

What actually happened? Please include any error messages given to you by Sass Lint.

Error: Rule no-vendor-prefixes could not be found!

Is this actually renamed to no-value-vendor-prefix? I dont find information in the changelog too. Please provide your valuable suggestion.

@kumaresan-subramani
Copy link

Hi Team,

While downloading version 1.12.1

no-vendor file exists refer below:

InkedMicrosoftTeams-image_LI

But in latest version this file name got changed as like below:

Screenshot (217)_LI

In your github source, the won't won't get changed. Refer below:

Screenshot (215)_LI

@DanPurdy
Copy link
Member

Basically it looks like there's been a bit of a mixup from one of our new maintainers - 1.13 should never of been released it should of been a v2.0 as it's full of breaking changes.

For now you should stick to v1.12.1 and not upgrade -
I tried to unpublish 1.13.0 without any luck from npm last night after it had been pushed out. I will try and release a 1.13.1 if i get a chance later today which will revert most of the changes that came out but allow you to use the latest AST.

@DanPurdy
Copy link
Member

DanPurdy commented Apr 26, 2019

Ok 1.13.1 is out now it is EXACTLY the same as 1.12.1 - please let me know if you have any other issues. Obviously this project has been remained fairly unmaintained in the last two years and all of the work that we had done sitting around for our v2 release got accidentally released

My fault essentially for abandoning the project and not leaving any other handover docs about what I'd done or where i'd got to and with the work. This has led to confusion with our new maintainers and accidents happen. I'll be working with them to make sure the changes you briefly saw get released as a proper v2 soon.

@DanPurdy
Copy link
Member

I'll keep this issue open to see if we get any further reports but for those just seeing this either lock your version to 1.12.1 or update to 1.13.1.

I will maybe look at getting the latest AST released as a 1.13.2 if i get a chance to test it if not then expect all the changes to be released in a new major update v2

@Madhust
Copy link
Author

Madhust commented Apr 26, 2019

@DanPurdy Thanks. Its working fine for me now.

@glen-84
Copy link
Contributor

glen-84 commented May 16, 2019

@DanPurdy @srowhani,

#995 was closed and then the release was reverted – can you please release this feature, or at least reopen that issue?

@gustavoalfaro
Copy link

Hey @DanPurdy is this project still waiting for the V2?

@Grawl
Copy link

Grawl commented Apr 16, 2020

Everyone here wants to get a first-class linter for .sass should try postcss-sass, a PostCSS syntax for .sass files to use with Stylelint.

I created a test repo to see how it works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants