Build toolBuild toolRuns at build time. Nothing of it ships in the deployed application.See every one →What this type is →independently maintainedindependently maintainedPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →
@cbs-consulting/tools
Shared ESLint configuration for SAPUI5 and CAP projects, the config rather than the rules, so a team adopts a house style by adding one dependency.
Facts
Latestv1.3.0ReleasedLicenceMIT License
Where it sits
What it declares
Every artifact
- Type
- Build tool
- Origin
- Independently maintained
As a build tool
- Declared for
- >=9
- Distributed through
- npm
Connections
Group by
NodeRelationBasis
Functional
LintingLintingCatching problems in code, models and configuration by rulesSAP and community, narrow by design
provides
authored
provides Linting
Catching problems in code, models and configuration by rules
Download
Install
npm add @cbs-consulting/toolsDerived from the package name. No recipe recorded; the README has the configuration.
README
quoted from @cbs-consulting/tools@1.3.0, read@cbs-consulting/tools@1.3.0/README.mdthe maintainer’s wordsOn npm
@cbs-consulting/tools
@cbs-consulting/tools is a configuration package that provides shared ESLint configurations for developing SAPUI5 and/or SAP Cloud Application Programming Model (SAP CAP) applications. Furthermore, it includes a Prettier configuration to ensure consistent code formatting across projects.
History
Others providing
Compare all 6 on the Linting page →LintingLintingCatching in the editor what would otherwise be caught at deploy time, or not at all — problems in source code and models and in the project's configuration, found by rules rather than by review.SAP and community, narrow by design
- @cbs-consulting/cds-eslint@cbs-consulting/cds-eslintAn ESLint plugin for CDS files carrying one consultancy's own rules, published so that the consultancy's projects lint their CDS models the same way.independent, capESLint plugin with one consultancy's rules for CDS files
- eslint-plugin-better-cap-configeslint-plugin-better-cap-configA set of ESLint rules that read CAP configuration and flag the cds settings that have since been deprecated, putting that check in the linter a project already runs, with no dependencies of its own.independent, capESLint rules flagging deprecated CAP configuration
- hana-linterhana-linterA command line that checks the names of the native SAP HANA artifact files in a CAP project, and the identifiers inside them, against regex rules the project keeps in a config file.independent, capRegex naming rules for SAP HANA artifacts in a CAP project
- @sap/eslint-plugin-cds@sap/eslint-plugin-cdsSAP's ESLint plugin for CDS, carrying the model and environment rules capire calls best practice and universal for every CAP project.sap official, capSAP's ESLint plugin for CDS
- @sap-ux/eslint-plugin-fiori-tools@sap-ux/eslint-plugin-fiori-toolsESLint rules from the Fiori tools team, aimed at the parts of a project their generators produce.sap official, capESLint rules for projects the Fiori tools generators produce
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
declared for>=9
latestv1.3.0
first release
releases and cadence8, ~0d median
discovered vianpm registry, The discovery pass
first seen in the atlas
ecosystem and domaincap, developer-experience
Flavors
Node.js
“npm install --save-dev @cbs-consulting/tools eslint @sap/cds @sap/eslint-plugin-cds” — @cbs-consulting/tools — npm README
History in the atlas
- npm: https://www.npmjs.com/package/@cbs-consulting/tools
- Typed cds-plugin by placement, which defaults every candidate to that. It is not one.
- Shared ESLint configuration for SAPUI5 and CAP projects — the config, not the rules, so a team adopts a house style in one dependency.
- First seen.
For your agent
- Ref
artifact:cbs-consulting-tools- JSON
- /artifacts/cbs-consulting-tools.json
- MCP
- Connecting an agent