TypeScript library starter
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 name.
- Zero-setup. After running
npm installthings will setup for you :wink:
- RollupJS for multiple optimized bundles following the standard convention and Tree-shaking
- Tests, coverage and interactive watch mode using Jest
- Prettier and TSLint for code formatting and consistency
- Docs automatic generation and deployment to
gh-pages, using TypeDoc
- Automatic types
- Travis integration and Coveralls report
- (Optional) Automatic releases and changelog, using Semantic release, Commitizen, Conventional changelog and Husky (for the git hooks)
You can import the generated bundle to use the whole library generated by this starter:
import myLib from 'mylib'
Additionally, you can import the transpiled modules from
dist/lib in case you have a modular library:
import something from 'mylib/dist/lib/something'
npm t: Run test suite
npm start: Run
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: Generate 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:)
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.
Good news: the setup is here for you, you must only include the dependency name in
external property within
rollup.config.js. For example, if you want to exclude
lodash, just write there
Prerequisites: you need to create/login accounts and add your project to:
Prerequisite for Windows: Semantic-release uses node-gyp so you will need to install Microsoft's windows-build-tools using this command:
npm install --global --production windows-build-tools
Follow the console instructions to install semantic release and run it (answer NO to "Do you want a
.travis.yml file with semantic-release setup?").
Note: make sure you've setup
repository.url in your
npm install -g semantic-release-cli semantic-release-cli setup # IMPORTANT!! Answer NO to "Do you want a `.travis.yml` file with semantic-release setup?" question. It 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 two disabled git hooks. They're set up when you run the
npm run semantic-release-prepare script. They make sure:
- You follow a conventional commit message
- Your build is not going to fail in Travis (or your CI server), since it's runned locally before
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 install doing on first run?
It runs the script
tools/init which sets up everything for you. In short, it:
- Configures RollupJS for the build, which creates the bundles
package.json(typings file, main file, etc)
- Renames main src and test files
What if I don't want git-hooks, automatic releases or semantic-release?
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
What if I don't want to use coveralls or report my coverage?
npm run report-coverage from
- Write a library using TypeScript library starter by @alexjoverm
- 📺 Create a TypeScript Library using typescript-library-starter by @alexjoverm
- Introducing TypeScript Library Starter Lite by @tonysneed
Here are some projects that use
- NOEL - A universal, human-centric, replayable event emitter
- droppable - A library to give file dropping super-powers to any HTML element.
- redis-messaging-manager - Pubsub messaging library, using redis and rxjs
Made with :heart: by @alexjoverm and all these wonderful contributors (emoji key):
This project follows the all-contributors specification. Contributions of any kind are welcome!