[![styled with prettier](https://img.shields.io/badge/styled_with-prettier-ff69b4.svg)](https://github.com/prettier/prettier) [![Greenkeeper badge](https://badges.greenkeeper.io/alexjoverm/typescript-library-starter.svg)](https://greenkeeper.io/) [![Travi
A starter project that makes creating a TypeScript library extremely easy.
git clone https://github.com/alexjoverm/typescript-library-starter.git YOURFOLDERNAME cd YOURFOLDERNAME # Run npm install and write your library name when asked. That's all! npm install
package.json and entry files are already set up for you, so don't worry about linking to your main file, typings, etc. Just keep those files with the same names.
npm installthings will be setup for you :wink:
gh-pages, using TypeDoc
On library development, one might want to set some peer dependencies, and thus remove those from the final bundle. You can see in Rollup docs how to do that.
The good news is here is setup for you, you only must include the dependency name in
external property within
rollup.config.js. For example, if you wanna exclude
lodash, just write there
npm t: Run test suite
npm start: Runs
npm run buildin watch mode
npm run test:watch: Run test suite in interactive watch mode
npm run test:prod: Run linting and generate coverage
npm run build: Generage bundles and typings, create docs
npm run lint: Lints code
npm run commit: Commit using conventional commit style (husky will tell you to use it if you haven't :wink:)
If you'd like to have automatic releases with Semantic Versioning, follow these simple steps.
Prerequisites: you need to create/login accounts and add your project to:
Run the following command to prepare hooks and stuff:
npm run semantic-release-prepare
Follow the console instructions to install semantic release run it (answer NO to "Generate travis.yml").
Note: make sure you've setup
repository.url in your
npm install -g semantic-release-cli semantic-release setup # IMPORTANT!! Answer NO to "Generate travis.yml" question. Is already prepared for you :P
From now on, you'll need to use
npm run commit, which is a convenient way to create conventional commits.
Automatic releases are possible thanks to semantic release, which publishes your code automatically on github and npm, plus generates automatically a changelog. This setup is highly influenced by Kent C. Dodds course on egghead.io
There is already set a
precommit hook for formatting your code with Prettier :nail_care:
By default, there are 2 disabled git hooks. They're set up when you run the
npm run semantic-release-prepare script. They make sure:
This makes more sense in combination with automatic releases
Map... is undefined?
TypeScript or Babel only provides down-emits on syntactical features (
async/await...), but not on functional features (
Promise...), . For that, you need Polyfills, such as
babel-polyfill (which extends
For a library,
core-js plays very nicely, since you can import just the polyfills you need:
import "core-js/fn/array/find" import "core-js/fn/string/includes" import "core-js/fn/promise" ...
npm installdoing the first time runned?
It runs the script
tools/init which sets up everything for you. In short, it:
package.json(typings file, main file, etc)
Then you may want to:
package.json. That will not use those git hooks to make sure you make a conventional commit
npm run semantic-releasefrom
npm run report-coverage from
???? ???? ????
This project follows the all-contributors specification. Contributions of any kind welcome!