changed-files
ESLint
changed-files | ESLint | |
---|---|---|
6 | 382 | |
1,521 | 24,310 | |
3.7% | 1.0% | |
9.8 | 9.7 | |
8 days ago | 7 days ago | |
TypeScript | 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.
changed-files
-
Why it is Important to Update Linters and How to Do it Right
We need to add two additional steps. The first one is to retrieve all new files, and the second one is to run the enhanced config only on the new files. In this example the third-party GitHub Action called changed-files is used to obtain the new files. In the GitHub Marketplace for Actions, there is a considerable number of similar actions with similar functionality. You can choose the one that suits you best, as the functionality is more or less the same for all of them.
-
Attempting a larger bug fix II - Execution
I determined this after dozens of attempts working with the other GitHub Action, tj-actions/changed-files which feeds a list of modified files to clang-format-lint.
-
Yarn workspaces/monorepo and CI/CD
GitHub actions has actions that do similar, I’ve used this one before with great success: https://github.com/tj-actions/changed-files
-
Turborepo + GitHub Actions
You could also clean up your changed files job by using this (https://github.com/tj-actions/changed-files) or something similar. That would at least make it easier to understand what it's supposed to be doing. You can use it to get the directories containing any changed package.json files. Then use that output as as a matrix input.
- GitHub Actions Pitfalls
-
GitHub Action to run mypy on changed files only
View on GitHub
ESLint
-
How to make ESLint and Prettier work together? 🛠️
Let's be honest - setting up tools for a new project can be a frustrating process. Especially when you want to jump straight to coding part. This is often the case with ESLint and Prettier, two popular tools in the JavaScript ecosystem that can sometimes interfere with each other when it comes to code formatting. Fortunately, there's a simple solution to this process, and it's called eslint-plugin-prettier.
-
Release Radar · April 2024 Edition: Major updates from the open source community
Do you have the need to find and fix problems in your JavaScript? Then ESLint is for you. With over 120 million downloads each month, it's definitely one of the most popular projects out there. The latest version introduces a new configuration system, designed to simplify available configuration options. Old and deprecated rules have been removed, and a new configuration inspector has been added. Check out the blog for all the highlights, and a migration guide.
-
Shared Data-Layer Setup For Micro Frontend Application with Nx Workspace
ESLint: A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript.
-
To Review or Not to Review: The Debate on Mandatory Code Reviews
Automating code checks with static code analysis allows us to enforce code styling effectively. By integrating tools into our workflow, we can identify errors at an early stage, while coding instead of blocking us at the end. For instance, flake8 checks Python code for style and errors, eslint performs similar checks for JavaScript, and prettier automatically formats code to maintain consistency.
-
Biome.js : Prettier+ESLint killer ?
If you're a developer, you're surely familiar with Prettier and ESLint. With over 8 years of existence, they have established themselves as references in the JavaScript ecosystem.
-
Most basic code formatting
eslint is used to avoid code errors
-
How to use Lefthooks in your node project?
No lint errors: The committed code does not contain any lint errors (eslint).
-
Git Project Configuration With Husky and ESLint
Let’s walk through the steps for a one-time setup to configure husky pre-commit and pre-push hooks, ESLint with code styles conventions, prettier code formatter, and lint-staged. Husky automatically runs a script on each commit or push. This is useful for linting files to enforce code styles that keeps the entire code base following conventions.
-
What is an Abstract Syntax Tree in Programming?
GitHub | Website
-
Shared Tailwind Setup For Micro Frontend Application with Nx Workspace
ESLint: A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript.
What are some alternatives?
actionlint - :octocat: Static checker for GitHub Actions workflow files
XO - ❤️ JavaScript/TypeScript linter (ESLint wrapper) with great defaults
Image-Optimizer-Action - A Github Action to optimize / compress images in your repository
Standard - 🌟 JavaScript Style Guide, with linter & automatic code fixer
paths-filter - Conditionally run actions based on files modified by PR, feature branch or pushed commits
prettier - Prettier is an opinionated code formatter.
runner-images - GitHub Actions runner images
JSHint - JSHint is a tool that helps to detect errors and potential problems in your JavaScript code
template.github.semver - Template for Projects that use Github Actions and Hooks to enforce Semantic Versioning
JSLint - JSLint, The JavaScript Code Quality and Coverage Tool
ansible-lint-action - ❗️Replaced by https://github.com/marketplace/actions/run-ansible-lint
Babel (Formerly 6to5) - 🐠 Babel is a compiler for writing next generation JavaScript.