Style guide for adding type definitions to my npm packages
by sindresorhusLast 12 weeks · 0 commits
4 of 6 standards met
Instead of a 590-words styleguide it could be shorter and the rest can be enforced by eslint, where automation is possible, like: Use tab-indentation and semicolons. Don't prefix the name of interfaces with ; , not : https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/interface-name-prefix.md Imports, destructuring, and object literals should not have spaces around the identifier; , not . Use the array shorthand type notation; number[], not Array. https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/no-array-constructor.md
Repository: sindresorhus/typescript-definition-style-guide. Description: Style guide for adding type definitions to my npm packages Stars: 574, Forks: 13. License: CC-BY-4.0. Topics: style-guide, typescript, typescript-definitions. Open PRs: 0, open issues: 0. Last activity: 3y ago. Community health: 71%. Top contributors: sindresorhus, BendingBender, shellscape, sonicdoe.