Danger for JS
Danger JS is a tool to creating complex per-project rules, and messages in Code Review. One of it's key aims is to be able to run on a server, and not need direct access to the filesystem to do its work.
It was started in mid-2016, and has fleshed out into a considerable set of useful tools.
- You can get started in a fun way via
- You can run danger via
- You can fake running on CI locally for any GitHub PR with
- You can run Danger rules inside git hooks, or without pull requests metadata via
- You can share code using danger plugins.
- Danger can run independently of CI via Peril.
There is only really one big target left for the future of Danger JS:
I don't plan on really using this, so I expect both to come from the community instead.
My focus is going to be mainly in the Peril side of Danger. Moving to making it trivial to add Danger to any GitHub project and really unlocking some complex culture systems. Examples of these can be found on the Artsy blog.
Why Danger JS? What about Danger Ruby?
When I started Danger JS, Danger Ruby was two years old, is still doing just fine. See the original vision file. This document assumes you have read it.
production) but this pattern isn't going to work on the larger scale: You cannot use npm modules, nor work with
babel/tsc to transpile your
Dangerfile.js and the requirements on the integrating project
feel weird. Running JS in Ruby isn't going to work for me.