stylelint
lint-staged
Our great sponsors
stylelint | lint-staged | |
---|---|---|
44 | 50 | |
10,821 | 12,858 | |
0.8% | 1.4% | |
9.6 | 8.4 | |
3 days ago | 3 days ago | |
JavaScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
stylelint
-
Why it is Important to Update Linters and How to Do it Right
Another common way to extend configs in linters is using the extends key in the configuration file. Let's take StyleLint as an example:
-
How to Improve Development Experience of your React Project
Stylelint is similar to ESLint, but its focus is on styling rather than JavaScript. It helps you find errors in style files, such as old syntax or empty classes. We will also incorporate stylelint-config-clean-order to sort your style rules and group them consistently across the entire codebase.
-
Speeding up the JavaScript ecosystem ā The barrel file debacle
The ācost of loading modulesā diagram shows non-linear behaviour (though you should largely ignore the curve visible in the diagram because the x axis is way off linear):
ā¢ 0.15s Ć· 500 = 0.3ms
ā¢ 0.31s Ć· 1000 = 0.31ms
ā¢ 3.12s Ć· 10000 = 0.312ms
ā¢ 16.81s Ć· 25000 = 0.6724ms
ā¢ 48.44s Ć· 50000 = 0.9688ms
My own observation on a Surface Book six years ago was that in Node.js under Windows, each module had about 1ms of overhead when there was warm file system cacheāthat is, simply bundling with Rollup saved 1ms per file. If this sort of thing interests you, quite a lot of useful stuff came out of https://github.com/stylelint/stylelint/issues/2454 which I filed because I was unhappy with stylelint taking over a second to import. And that must have been only in the order of one or two thousand modules, when the behaviour is still close enough to linear.
-
Don't sound like a robot: use CSS to Control Text-to-Speech
As the property is still experimental, stylelint does not recognize it yet at the time of writing this, so let's explicitly disable the property-no-unknown rule only where we use it by adding a stylelint-disable comment and re-enable it afterwards.
-
How to upskill my skills?
Document your build process in a blog, use eslint, stylelint and jsx-a11y lint. Run a lighthouse performance test, follow the optimisation reccomendations.
-
How to Effortlessly Improve a Legacy Codebase Using Robots
Run static analysis e.g. lint with lockfile-lint, Stylelint, ESLint, check for unimported files using unimported, and identify potential security vulnerabilities
-
10 CSS Tools AI Can Integrate With for Improved Website Design
Stylelint
-
How can I have CSS automatically formatted so that all of the properties are in order by length, as I type?
I use StyleLint (https://stylelint.io/) to lint my css/scss. I don't think that's a rule, but writing a custom rule isn't too tough. And you can use the vscode extension - https://marketplace.visualstudio.com/items?itemName=stylelint.vscode-stylelint
-
Deno Fresh PostCSS: Future CSS with Deno
The complete code for this project is in the Rodney Lab GitHub repo. I do hope the post has either helped you with an existing project or provided some inspiration for a new one. As an extension, you can add all your favourite future CSS rules to the PostCSS config. Beyond PostCSS for linting your input CSS, consider trying stylelint.
- This missing comma ruined my day. Can I get VSCode to fix this mistake automatically?
lint-staged
-
How Automation Saved Me from Oops Moments: Never Skip Tests in Production Again!
We were already using lint-staged and have a pre-commit hook in place using Husky in our project for linter and prettier. So it made sense to add a check here.
-
Pre-commit with husky & lint-staged
Now you can config it in your package.json, here is the guide doc:
-
Automating code patterns with Husky
In the world of software development, maintaining consistent code quality and ensuring that the codebase adheres to predefined patterns and guidelines is crucial. However, manually enforcing these standards can be time-consuming and error-prone. This is where automation tools like Husky, Lint-Staged, Commitlint, and Commitizen come to the rescue. In this post, we will explore how these tools can be combined to streamline your development workflow.
-
500 lines in 2013 is 10k in 2023, inflation you know
This is wasted work that can and should be automated. Adding a linter and formatter on CI and a pre-commit hook such as lint-staged can do wonders.
-
Set up linting and formatting for code and (S)CSS files in a Next.js project
lint-staged is a package that can be used to run formatting and linting commands on staged files in a Git repo.
-
How do you handle eslint/prettier configs across multiple repos?
To answer your next question: I lint and format on save, and I use Git hooks installed by Husky and executed through Lint-Staged (this tool helps ensure your Git hooks only run on modified files, etc) to ensure there are no lint or formatting errors whenever making a commit or pushing code. This is helpful for teams, as some developers tend to forget to run lint tasks, or don't have the Prettier extension installed in their IDE. If there are lint errors, the commit is rejected until fixed. YMMV - you'll need to fine-tune the strictness of this based on the team's needs.
-
How to create and publish a TypeScript library with ease
Uses Husky Git hooks and Lint-staged pre-commit hooks.
-
How to Contribute on the First Day of a FrontendĀ Project
Something else to consider is applying linting and formatting before every git commit. A package like Lint-staged only lints and formats on staged items, ensuring all pushed code follows the standards in the repo. This allows developers to have their own formatting preferences when developing, while the code homogenizes on push. Linting pre-commit also avoids strict rules like no-console or no-unused-vars restricting a developer when writing code, when it should only apply in production. Imagine not being able to console log anything during development!
-
Commit Like a PRO
Lint-Staged Docs
-
How to beautify your code and make contributions easy?
Additionally, there are pre-commit hooks which can be setup to seamlessly validate and modify the source code before every commit. I followed Prettier documentation to create one. I ran npx mrm@2 lint-staged which installed husky and lint-stagedand added a configuration to the projectās package.json. Then, I modified the commands a little and that's it.
What are some alternatives?
Next.js - The React Framework
commitlint - š Lint commit messages
Nest - A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript š
Symfony Encore - A simple but powerful API for processing & compiling assets built around Webpack
prettier - Prettier is an opinionated code formatter.
Nuxt.js - Nuxt is an intuitive and extendable way to create type-safe, performant and production-grade full-stack web apps and websites with Vue 3. [Moved to: https://github.com/nuxt/nuxt]
graphql-code-generator - A tool for generating code based on a GraphQL schema and GraphQL operations (query/mutation/subscription), with flexible support for custom plugins.
husky - Git hooks made easy š¶ woof!
volar - ā” Explore high-performance tooling for Vue [Moved to: https://github.com/vuejs/language-tools]
postcss-rtl - PostCSS plugin for RTL-adaptivity
pre-commit - A framework for managing and maintaining multi-language pre-commit hooks.