Stricter: ESlint for projects
0 likes203 views
This document outlines the functionalities of 'stricter', a tool used for managing ESLint configurations in large projects with over 200 monthly contributors. It automates guidelines for application structure and code formatting while analyzing project dependencies to report on bad patterns. Additionally, it supports various output formats and includes features like circular dependency detection and manifest validation for project organization.
![MANIFEST-VALIDATION
{
"contactStaffId": "Homer",
"team": "Simpsons",
"slackChannel": “#simpsons",
"jiraProjectUrl": “http://example.com",
"maintainers": ["Bart", "Liza"]
}
Sample manifest.json
└─foo
├─index.js
├─test.js
├─manifest.json
└─bar
├─index.js
└─test.js
└─baz
├─index.js
└─test.js
Missing
manifest.json](https://image.slidesharecdn.com/stricter-190829005420/85/Stricter-ESlint-for-projects-12-320.jpg)
![FASTER BUILDS
Use stricter to
speed up your
branch builds
parseDependencies(files: string[]): FileToDependency](https://image.slidesharecdn.com/stricter-190829005420/85/Stricter-ESlint-for-projects-16-320.jpg)
Stricter: ESlint for projects
- 1. ALEXEY SHPAKOV | ATLASSIAN Stricter: ESlint for projects
- 2. 200+ monthly contributors In different timezones and remote Jira Frontend 1.5M+ lines of code And growing 30+ teams With different goals
- 3. 🍊Tangerine Through guidelines defines the ideal shape of the repo
- 4. ESlint Code style Automating the guidelines ? Application structure Prettier Code formatting
- 5. Is a tool to analyse dependency graph and project structure and report on bad patterns. STRICTER https://github.com/stricter/stricter
- 6. Scan files Caches data to speed up subsequent runs Build a dependencies graph Uses babel to parse files and node dependency resolution algorithm Run rules Supports blacklist and whitelist Report results Supports console, mocha, junit How stricter works
- 8. UNUSED-FILES (OPEN-SOURCE) ├─entry-point.js ├─component.js ├─test.js ├─story.js └─mocks.js Are mocks used by tests/stories for orphaned functionality? Does it test orphaned functionality? Does it showcase orphaned functionality? Is it orphaned?
- 9. PROJECT-STRUCTURE config: { definitions: { '.': 'app', app: { view: 'view', state: { type: DIR, optional: true }, 'index.js': FILE, 'test.js': FILE, }, view: { 'index.js': FILE, 'view.js': { type: FILE, optional: true }, 'test.js': { type: FILE, optional: true }, assets: { type: DIR, optional: true }, '*': 'view', }, }, }, └─foo ├─index.js ├─test.js └─view ├─index.js └─component-bar ├─index.js └─assets └─component-baz └─assets Missing index.js
- 10. PURELY-DUMB-COMPONENTS container-a.js presentational.js container-b.js presentational.js is not allowed to import container-b.js
- 11. FLOW-DEPENDENCY-REQUIREMENT foo.js // no flow bar.js // flow baz.js // no flow foo.js is not allowed to import bar.js
- 12. MANIFEST-VALIDATION { "contactStaffId": "Homer", "team": "Simpsons", "slackChannel": “#simpsons", "jiraProjectUrl": “http://example.com", "maintainers": ["Bart", "Liza"] } Sample manifest.json └─foo ├─index.js ├─test.js ├─manifest.json └─bar ├─index.js └─test.js └─baz ├─index.js └─test.js Missing manifest.json
- 13. TANGERINE-APP-ENFORCER/TANGERINE-DEPENDENCIES └─app-foo └─index.js └─app-bar ├─index.js └─view ├─index.js └─baz └─index.js app-foo/index.js could only access app-bar/index.js app-bar/view/baz/index.js could not reach out upwards
- 14. More rules Coming soon Typescript support Improved documentation Extension for VS Code Test coverage
- 15. One more thing
- 16. FASTER BUILDS Use stricter to speed up your branch builds parseDependencies(files: string[]): FileToDependency
- 18. Thank you