If you love software workflows as much as I do, you should check out my basics for deploying NPM packages using TypeScript, CircleCI v2, and GitHub Releases.
You can find an example project on GitHub configured with all of following features. Use this guide as documentation for the project and make sure to check out the sources!
GitHub and The Basics
Just work with GitHub as you are used to: Work in branches, create Pull requests, ensure an always building
master branch, and think about why you might be using git wrong.
CircleCI v2 Workflows
The recent major release v2 of CircleCI introduced new features for Jobs and Workflows. You can split up the build process of your projects into smaller jobs that can be organized in workflows.
Each step for the NPM package is separated in single jobs, so tasks for running the tests and linting the source files can be run in parallel.
With the basic GitHow flow, this works perfectly: Every commit on a branch and new Pull requests trigger the following NPM tasks:
lint- Check the sources
test- Run all tests
build- Ensure the project can be build
coverage- Post coverage report to Coveralls.io
test are executed at the same time in parallel. After both tasks finished successfully, CircleCI triggers the jobs for
coverage, in parallel of course.
Publish to NPM
On top of the basics for every branch and PullRequest, CircleCI is configured to run the
deploy task for every GitHub Release after building the project was successful.
With this workflow, you will always have tests, linting, and compile checks for every branch and PR. You can manage your changelog with GitHub Releases and don’t have to care about how to publish your project to NPM.
Just configure CircleCI with your NPM token, and for every release a new NPM package with that version is published:
You can find plenty of frameworks and tools to provision your AWS resources. Some of them do a great job for a specific purpose, others are more generic. Nevertheless, I do prefer to use native CloudFormation templates as much as possible.605 words, posted on May 1
The more projects you work on, the more streamlined your tooling gets. Hopefully. Various services using different languages have different tooling requirements, of course. A sweet Makefile can be the entry to a unified tooling interface.263 words, posted on April 30
With AWS AppSync, it’s easy to run your own serverless GraphQL service API. Thanks to Velocity Mapping Templates, DynamoDB, and AWS Lambda your can aim for an architecture without any maintenance at all.280 words, posted on April 7