# linter Published articles for linter. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## tota11y - an accessibility visualization toolkit DevFeed: [tota11y - an accessibility visualization toolkit]() Original publisher: [Read original article]() Author: Khan Academy Published: 2015-06-08T22:00:00Z Content type: release Language: en Sources: [Khan Academy]() Topics: [Accessibility](), [audit](), [Testing](), [Tooling](), [browser](), [Chrome]() Tags: [accessibility](), [accessibility-testing](), [audit](), [browser](), [chrome](), [developer-tools](), [engineering](), [frontend](), [linter](), [news](), [testing](), [tests](), [tooling](), [unit-tests](), [visualization](), [web](), [web-frontend]() ### AI overview Khan Academy announces tota11y, an accessibility visualization toolkit designed to make manual accessibility testing easier for developers. The article describes its development and use of browser-based annotations to help teams understand and fix accessibility issues. ### Source excerpt By Jordan Scales Today we're releasing tota11y (on GitHub), an accessibility visualization toolkit that aims to reduce the ... Read more ## Checking code with lint, formatting it with prettier DevFeed: [Checking code with lint, formatting it with prettier]() Original publisher: [Read original article]() Author: T.J. Maher (noreply@blogger.com) Published: 2026-08-10T23:23:45Z Content type: tutorial Language: en Sources: [T.J. Maher]() Topics: [ESLint](), [Prettier](), [Playwright](), [Programming]() Tags: [bun](), [bun-create-playwright](), [eslint](), [formatting](), [linter](), [playwright](), [typescript]() ### AI overview This tutorial explains how to add ESLint for static analysis and Prettier for consistent code formatting in a Playwright project. It also discusses eslint-plugin-playwright and using eslint-config-prettier to reduce conflicts between ESLint and Prettier. ### Source excerpt Now that we've installed bun, Anthropic's package manager, scaffolded a Playwright framework and closely examined the results, and added typechecking with TypeScript's compiler, it's time to add ways to check the code with lint, and reformat the code with prettier. We will be using: ESLint, as the static-analysis tool to review the code without running it. Little bits of fluff -- like syntax errors, structural bugs, anti-patterns, and code style violations -- can collect on your code, so it helps to run a linter to help catch it all, such as ESLint. There is also a linter, eslint-plugin-playwright, for Playwright tests. Prettier enforces a consistent code style across your entire codebase. Because ESLint and Prettier can conflict, we will be using Prettier's eslint-config-prettier, which turns off all rules that are unnecessary or might conflict with ESLint. What is a Linter? According to the Wikiwand entry for Lint, "Stephen C. Johnson, a computer scientist at Bell Labs, came up with the term 'lint' in 1978 while debugging the yacc grammar he was writing for C and dealing with portability issues stemming from porting Unix to a 32-bit machine. The term was borrowed from lint, the tiny bits of fiber and fluff shed by clothing, as the command he wrote would act like a lint trap in a clothes dryer, capturing waste fibers while leaving whole fabrics intact. The lint program was released outside of Bell Labs in Unix V7, in 1979. "In his 1978 paper, Johnson explained his reasons for creating a new program to detect errors: '...the general notion of having two programs is a good one' because they concentrate on different things, thereby allowing the programmer to 'concentrate at one stage of the programming process solely on the algorithms, data structures, and correctness of the program, and then later retrofit, with the aid of lint, the desirable properties of universality and portability' " What is ESLint? Website: https://eslint.org/ GitHub: https://github.com/eslint/e ## YAML for DevOps Beginners, Syntax, Rules and Common Mistakes DevFeed: [YAML for DevOps Beginners, Syntax, Rules and Common Mistakes]() Original publisher: [Read original article]() Author: Pramodh Kumar M Published: 2026-08-06T17:16:19Z Content type: tutorial Language: en Sources: [Kubernetes - KodeKloud Blog | DevOps, Cloud, Kubernetes, AI Tutorials & More]() Topics: [YAML](), [configuration](), [DevOps](), [Ansible](), [ci](), [Kubernetes]() Tags: [ansible](), [block-scalars](), [ci-cd](), [cloud](), [configuration](), [devops](), [errors](), [guide](), [how-to](), [json](), [kubernetes](), [kubernetes-yaml-manifests](), [linter](), [mistakes](), [multi-document-yaml](), [structure](), [syntax](), [validation](), [yaml](), [yaml-anchors-and-aliases](), [yaml-common-mistakes](), [yaml-for-devops](), [yaml-indentation-rules](), [yaml-norway-problem](), [yaml-syntax-rules](), [yaml-vs-json](), [yamllint-validation]() ### AI overview A tutorial explaining YAML syntax, implicit typing, indentation rules, block scalars, anchors, aliases, and merge keys. It emphasizes that YAML can silently reinterpret unquoted values and recommends linting and schema validation in CI pipelines. ### Source excerpt YAML tries to guess what you meant, and that is the entire problem. Once you know which values it silently reinterprets and why, the manifests that mysteriously break stop being mysterious. ## AI Coding Tip 027 - Force Code Standards DevFeed: [AI Coding Tip 027 - Force Code Standards]() Original publisher: [Read original article]() Author: Maxi Contieri Published: 2026-07-10T14:24:14Z Content type: tutorial Language: en Sources: [Maximiliano Contieri - Software Design]() Topics: [ai-coding](), [coding](), [pull-requests](), [Language models]() Tags: [agents](), [ai-coding](), [analysis](), [code](), [coding](), [harness](), [hooks](), [how-to](), [large-language-model](), [linter](), [pull-request](), [reviews](), [skills](), [trust](), [windows]() ### AI overview A tutorial on enforcing coding standards in AI-assisted development. It recommends converting prose standards into machine-checkable rules, running them through hooks and validator skills, and using an LLM judge for ambiguous semantic violations before code reaches human review. ### Source excerpt TL;DR: Wire your standards into hooks, skills, and a judge, so the harness blocks violations before a human opens the diff. Common Mistake ❌ You paste your coding standards into AGENTS.md and trust t ## OpenAI Eng & Dev Tools Founder: How Software Engineering Is Changing | Charlie Marsh DevFeed: [OpenAI Eng & Dev Tools Founder: How Software Engineering Is Changing | Charlie Marsh]() Original publisher: [Read original article]() Author: Ryan Peterman Published: 2026-06-22T09:45:53Z Content type: article Language: en Sources: [The Developing Dev]() Topics: [dev-tools](), [Development](), [Python](), [Software Engineering](), [engineering-culture]() Tags: [dev](), [dev-tools](), [engineering](), [go](), [javascript](), [linter](), [openai](), [python](), [rust](), [software-engineering](), [tooling](), [tools]() ### AI overview An interview with Charlie Marsh, founder of Astral, examines how software engineering and developer tooling are changing. Marsh discusses his experience building Python systems, limitations in Python tooling, and the influence of performance-focused native tools in the JavaScript ecosystem. ### Source excerpt Charlie Marsh is the founder of Astral, the Python devtool startup that was acquired by OpenAI. ## How To Type Function Mocha Context With Cypress Aliases DevFeed: [How To Type Function Mocha Context With Cypress Aliases]() Original publisher: [Read original article]() Author: Gleb Bahmutov Published: 2025-12-11T05:00:00Z Content type: tutorial Language: en Sources: [Gleb Bahmutov]() Topics: [Cypress](), [Mocha](), [interfaces](), [test]() Tags: [argument](), [callback](), [code](), [cypress](), [how-to](), [interface](), [interfaces](), [linter](), [products](), [test](), [typescript]() ### AI overview This tutorial explains how to add strong typing for the custom property Cypress aliases place on the Mocha test context. It shows how to extend the relevant callback context type when the bundled type is not directly exposed. ### Source excerpt In Cypress you can save values under aliases which is pretty handy. You can get the aliased value ## React 19.2 DevFeed: [React 19.2]() Original publisher: [Read original article]() Author: The React Team Published: 2025-10-01T00:00:00Z Content type: article Language: en Sources: [React Blog]() Topics: [React](), [Web Development]() Tags: [2025](), [linter](), [new-features](), [npm](), [performance](), [react](), [release](), [state]() ### AI overview React 19.2 introduces Activity for prioritizing hidden and visible UI work, React Performance Tracks, and useEffectEvent for separating event logic from Effects. The release also improves pre-rendering, background loading, navigation performance, and state preservation. ### Source excerpt React 19.2 adds new features like Activity, React Performance Tracks, useEffectEvent, and more. ## What Is Linting? DevFeed: [What Is Linting?]() Original publisher: [Read original article]() Author: John Caleb Published: 2025-07-04T04:23:28Z Content type: tutorial Language: en Sources: [Baeldung - CS]() Topics: [developer tooling](), [Code quality](), [Parsing](), [JavaScript](), [Programming]() Tags: [automated](), [code-analysis](), [code-quality](), [compilers-and-linkers](), [javascript](), [lint](), [linter](), [parsing](), [programming](), [programming-compilers-and-linkers](), [quality-control](), [readability](), [syntax]() ### AI overview This tutorial explains what linting is, why linters are useful in software development, and how they detect syntax, semantic, formatting, and coding-style problems. It describes parsing source code into an abstract syntax tree and applying rules to identify issues such as undefined variables and incorrect code usage. ### Source excerpt Explore linters, tools for automated code analysis that can capture syntactic, semantic, and stylistic errors in code. The post What Is Linting? first appeared on Baeldung on Computer Science. Related Stories How to Start Building an Operating System Raft Consensus Algorithm What Is a Monad? ## Suppressions of Suppressions DevFeed: [Suppressions of Suppressions]() Original publisher: [Read original article]() Published: 2025-06-11T00:00:00Z Content type: article Language: en Sources: [Dan Abramov]() Topics: [Code](), [ci](), [syntax](), [Open Source]() Tags: [ci](), [code](), [false-positives](), [lint](), [linter](), [open-source](), [rules]() ### AI overview The article examines lint-rule suppressions: they can handle false positives and gradual rule adoption, but suppressing certain rules may cause serious problems. It proposes a lint rule that prevents suppression of selected other rules and notes that this protection can itself be suppressed. ### Source excerpt I heard you like linting. ## React Compiler Beta Release DevFeed: [React Compiler Beta Release]() Original publisher: [Read original article]() Author: Lauren Tan Published: 2024-10-21T00:00:00Z Content type: article Language: en Sources: [React Blog]() Topics: [Compiler](), [React](), [ESLint](), [Open Source](), [npm]() Tags: [bug](), [build](), [community](), [compiler](), [eslint](), [experimental](), [linter](), [npm](), [open-source](), [react](), [release]() ### AI overview React Compiler Beta is now available for early adopters and library maintainers. The build-time tool automatically memoizes React applications, supports React 17 and later, and is accompanied by an ESLint plugin that helps identify Rules of React violations. The React team also opened public membership in the React Compiler Working Group to gather feedback and support gradual adoption. ### Source excerpt At React Conf 2024, we announced the experimental release of React Compiler, a build-time tool that optimizes your React app through automatic memoization. In this post, we want to share what's next for open source, and our progress on the compiler. ## Enforce schema consistency across federated graphs with GraphOS DevFeed: [Enforce schema consistency across federated graphs with GraphOS]() Original publisher: [Read original article]() Author: Vivek Ravishankar Published: 2023-08-24T15:37:06Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [GraphOS](), [GraphQL](), [consistency](), [API Platform](), [Back end](), [CI/CD]() Tags: [announcement](), [backend](), [ci-cd](), [consistency](), [graphos](), [graphql](), [guide](), [linter](), [platform](), [schema]() ### AI overview Apollo GraphOS adds composition rules to its schema linter, enabling API platform teams to enforce consistency across federated GraphQL subgraphs. Teams can configure rule severity and apply checks in CI/CD pipelines or the GraphOS registry. ### Source excerpt When you're building a federated GraphQL API that spans multiple backend teams and services, it can be difficult to ensure that the schema for your graph stays consistent from subgraph to subgraph. For example, how do you ensure that a type defined as an entity in one subgraph is also defined as an entity in all other subgraphs? Today, we're making it easier for API platform teams to enforce schema consistency across multiple subgraphs by adding composition rules to the Apollo GraphOS linter. ## Standardize GraphQL schema linting policies with GraphOS DevFeed: [Standardize GraphQL schema linting policies with GraphOS]() Original publisher: [Read original article]() Author: Vivek Ravishankar Published: 2023-06-15T08:29:00Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [GraphOS](), [GraphQL](), [Structured-data](), [API](), [CI/CD](), [Command-line interface](), [Development](), [consistency]() Tags: [announcement](), [apis](), [ci-cd-pipeline](), [cli](), [consistency](), [graphos](), [graphql](), [lint](), [linter](), [schema]() ### AI overview Apollo GraphOS adds schema linting for GraphQL APIs. The checks validate predefined formatting and naming rules, run automatically when schema changes are published, and can also be run locally or in CI/CD pipelines with the Rover CLI. The feature is available to organizations on GraphOS Enterprise and Serverless plans. ### Source excerpt When it comes to writing code collaboratively, consistency is everything. APIs are no exception. In fact, APIs are perhaps the most important place to ensure consistency, since they act as a vein for collaboration across nearly every developer in an organization's ecosystem. For GraphQL APIs, the schema is at the heart of all collaboration and consumption, but ensuring consistency in a graph that spans many teams, tools, and workflows is no easy task. ## When Android Compat Libraries Do Not Prevent New API Compatibility Issues DevFeed: [When Android Compat Libraries Do Not Prevent New API Compatibility Issues]() Original publisher: [Read original article]() Author: Danny Preussler Published: 2021-01-04T19:34:03Z Content type: tutorial Language: en Sources: [Stories by Danny Preussler on Medium]() Topics: [Android](), [Jetpack](), [deprecated](), [Mobile]() Tags: [android](), [android-app-development](), [androiddev](), [compiler](), [deprecated](), [fragmentation](), [jetpack](), [kotlin](), [linter]() ### AI overview This tutorial explains why Android compatibility libraries do not all work the same way. Some duplicate platform APIs, while others bridge to the original APIs, so developers still need appropriate API-level checks and should avoid using the "NewApi" suppression indiscriminately. ### Source excerpt And why you should avoid using the "NewApi" suppression! https://unsplash.com/photos/EgGIPA68Nwo The idea of "Compat" libraries was probably one of the key aspects of Android dominating the mobile space. Other than with iOS, Android users often could not update their operating system after a new version launch, simply as their phones won't allow them to, the Android problem of fragmentation. But developers still wanted to use the latest features to compete. The solution was simple: instead of adding new APIs to the operating system, you shipped those directly with your app by using a "backport" version Google gave you. It all started with ActionBar Sherlock by Jake Wharton then got adopted by Google with in their "support libraries". Later on, this was mirrored as AndroidX under the Jetpack umbrella. Same but different Under the hood, not all of those "compat"-APIs are made the same way. Some, like the ones for Fragments, are complete copies of the code. You either use android.app.Fragment from the OS (actually deprecated) or androidx.fragment.app.Fragment. Both don't share any code or have a common base class (which is why we also have two versions of the FragmentManager). On the other handAppCompatActivity for example, simply extends the original Activity. AlsoAppCompatImageButton still is an ImageButton! We can see that sometimes these "Compat"-classes are just a "bridge" to add missing functionalities and sometimes they are complete duplicates. Let's look at another example! One area that changed a lot over time is the notification API from Android. There was a time where every Google I/O introduced a new API change. Good that we have NotificationManagerCompat to save us!? If, for example, we need to get the notification channel groups: val groups = notificationManagerCompat.notificationChannelGroups We don't need to worry about the groups being supported on all OS versions, as it is handled under the hood for us: public List getNotific ## Writing Resilient Components DevFeed: [Writing Resilient Components]() Original publisher: [Read original article]() Published: 2019-03-16T00:00:00Z Content type: opinion Language: en Sources: [Dan Abramov]() Topics: [React](), [Web Development]() Tags: [linter](), [opinion](), [react](), [style-guide]() ### AI overview An opinionated discussion of React component design that questions strict, linter-enforced style guides. It argues that flexible conventions can support integration, while excessive style rules may create friction, obscure useful warnings, and encourage technically unhelpful enforcement. ### Source excerpt Four principles to set you on the right path. ## Improve productivity with TypeScript and lifecycle hooks for Cloud Functions DevFeed: [Improve productivity with TypeScript and lifecycle hooks for Cloud Functions]() Original publisher: [Read original article]() Author: Thomas Bouldin Published: 2017-12-08T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [TypeScript](), [Cloud Functions](), [Firebase](), [JavaScript](), [Command-line interface]() Tags: [cloud-functions](), [deployment](), [firebase](), [firebase-cli](), [lifecycle](), [lint](), [linter](), [typescript]() ### AI overview The Firebase CLI added first-class TypeScript support for Cloud Functions starting with version 3.16.0. New TypeScript projects are configured for compilation, automatic transpilation during deployment, and recommended linting with TSLint. The article also explains lifecycle hooks such as predeploy and postdeploy. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Announcing our Experimental Linter Tool for Firebase on iOS DevFeed: [Announcing our Experimental Linter Tool for Firebase on iOS]() Original publisher: [Read original article]() Author: Ibrahim Ulukaya Published: 2017-08-17T00:00:00Z Content type: release Language: en Sources: [Firebase Blog]() Topics: [Swift](), [iOS](), [Xcode](), [SDKs](), [Objective-C]() Tags: [build](), [c](), [code](), [development](), [display](), [download](), [experimental](), [firebase](), [ios](), [launch](), [linter](), [news](), [pkg](), [pre-release](), [project](), [sdk](), [source](), [swift](), [tutorials](), [updates](), [us](), [xcode]() ### AI overview Firebase introduces experimental SwiftLint rules that warn about common mistakes when using the Firebase SDK in Swift projects. The rules are available through a Firebase fork and a pre-release binary, with instructions for installation and use in Xcode projects. ### Source excerpt News, tutorials, and updates from the Firebase team. ## Perfect Workflow in Sublime Text 2 DevFeed: [Perfect Workflow in Sublime Text 2]() Original publisher: [Read original article]() Published: 2013-05-05T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Sublime Text](), [Tutorial](), [Code]() Tags: [code](), [coding](), [linter](), [plugins](), [search](), [tutorial](), [tutorials]() ### AI overview A short recommendation of a Tuts+ tutorial covering Sublime Text 2 features and workflow techniques, including multiple cursors, fuzzy search, the Command Palette, Package Control, code snippets, and plugins. The tutorial is available as individual sessions or as a single YouTube video. ### Source excerpt Lorem ipsum dolor sit amet