a sharable linter as npm package
Shared linter configurations for TypeScript projects.
Shared linter configurations for TypeScript projects.
Codeverse's shared linter configuration
Shared linter settings for HotelQuickly
Shared linter and prettier configs, widely used in projects.
Shared linter settings
Utilities to help expose prettier output in linting tools
shared linter config for workspace
Default linter plugin for oas-validator
My shareable ESLint configuration for React projects.
Is this value a JS SharedArrayBuffer?
Core functions & classes shared by multiple AWS SDK clients.
[](https://www.npmjs.com/package/@smithy/core) [](https://www.npmjs.com/package/@smithy/core)
internal utils shared across @vue packages
Mozilla Add-ons Linter
ESLint plugin for formatjs
> Internal utility types shared across @vue/devtools packages.
The Linter plugin for Nx contains executors, generators and utilities used for linting JavaScript/TypeScript projects within an Nx workspace.
Shared configuration utilities for Herb tools
A stylelint plugin that harnesses the power of postcss-bem-linter
HTML+ERB linter for validating HTML structure and enforcing best practices
Command line tool and package to validate GraphQL schemas against a set of rules.
Spectrum UI components in React
Shared Rake tasks, linters, and build tooling for RatatuiRuby ecosystem gems.
The Apigee Registry API allows teams to upload and share machine-readable descriptions of APIs that are in use and in development. These descriptions include API specifications in standard formats like OpenAPI, the Google API Discovery Service Format, and the Protocol Buffers Language. These API specifications can be used by tools like linters, browsers, documentation generators, test runners, proxies, and API client and server generators. The Registry API itself can be seen as a machine-readable enterprise API catalog designed to back online directories, portals, and workflow managers.
The Apigee Registry API allows teams to upload and share machine-readable descriptions of APIs that are in use and in development. These descriptions include API specifications in standard formats like OpenAPI, the Google API Discovery Service Format, and the Protocol Buffers Language. These API specifications can be used by tools like linters, browsers, documentation generators, test runners, proxies, and API client and server generators. The Registry API itself can be seen as a machine-readable enterprise API catalog designed to back online directories, portals, and workflow managers. Note that google-cloud-apigee_registry-v1 is a version-specific client library. For most uses, we recommend installing the main client library google-cloud-apigee_registry instead. See the readme for more details.