Last 12 weeks · 0 commits
4 of 6 standards met
I would like to see a TypeScript boilerplate with yeoman support. I created a module from this and adapted it to TypeScript usage. As it uses tslint-xo, your tsconfig and Ava I think it is fitting to be added to your set of boilerplates. I can adapt it to be a boilerplate and create a PR for it but I am not sure if this repository is fitting. Also I am not sure about the workflow to decide between CLI, JavaScript or TypeScript within the yeoman generator. I would like feedback first. The node module I created: https://github.com/EdJoPaTo/angle-distance Please check it out and review it as a basic TypeScript module. This raised the question why there are multiple approaches for linting with TypeScript. This also might be useful to answer for ongoing migrations to TypeScript like sindresorhus/got. There is tslint-xo and xo with eslint-config-xo-typescript. Why are there both? Which one should be used? Should there be a xo-typescript package that handles everything useful to reduce clutter in the user projects and to reduce mistakes? (For example I only import xo instead of importing a bunch of eslint packages → way less prone to errors) Currently used scenarios: sindresorhus/is uses tslint-xo sindresorhus/caprine uses eslint-config-xo-typescript sindresorhus/got is using both
Repository: sindresorhus/node-module-boilerplate. Description: Boilerplate to kickstart creating a Node.js module Stars: 745, Forks: 74. Primary language: JavaScript. Languages: JavaScript (100%). License: MIT. Topics: node-boilerplate, node-module, nodejs, npm-package, template-repository. Open PRs: 0, open issues: 1. Last activity: 1y ago. Community health: 71%. Top contributors: sindresorhus, arthurvr, muhashi, kevva, blewisio, Zertz, Richienb.