Of course this needs a whole major version change due to the breaking changes
Description
The decision of adding the @stylistic package was based on the fact that these rules were already being used by the NC config. So for me it makes sense to keep them even if this deviates from the general approach that Stylelint has decided to keep.
Note that these rules were already lost in v2 of the NC rules, because after Stylelint v15 they had to be manually enabled again in the project, due to them being removed in the stylelint standard configuration.
The configuration has been tested with my own project, and is working as expected. There're a few new warnings being raised by the no-unsupported-browser-features plugin, so the Readme was updated with the newest recommendations
Related Issue
Fixes #17
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
[x] My code follows the code style of this project.
This PR does 2 main things:
Of course this needs a whole major version change due to the breaking changes
Description
The decision of adding the @stylistic package was based on the fact that these rules were already being used by the NC config. So for me it makes sense to keep them even if this deviates from the general approach that Stylelint has decided to keep.
Note that these rules were already lost in v2 of the NC rules, because after Stylelint v15 they had to be manually enabled again in the project, due to them being removed in the stylelint standard configuration.
The configuration has been tested with my own project, and is working as expected. There're a few new warnings being raised by the no-unsupported-browser-features plugin, so the Readme was updated with the newest recommendations
Related Issue
Fixes #17
Types of changes
Checklist: