Skip to content
A modern static build tool, powered by webpack
Branch: master
Clone or download

Latest commit

Latest commit 3030b2d Feb 7, 2019


Type Name Latest commit message Commit time
Failed to load latest commit information.
bin Update to next spike version + fixes (#50) Apr 5, 2017
lib update deps Jun 19, 2018
test fix list test Aug 23, 2017
.editorconfig initial commit May 13, 2016
.gitignore initial commit May 13, 2016
.npmignore update deps, add analytics note to readme Oct 20, 2016
.travis.yml initial commit May 13, 2016 readme updates May 13, 2016 add license Sep 6, 2016
package.json v2.3.0 Jul 27, 2018 maintenance badge Feb 7, 2019
yarn.lock update dependencies Jul 27, 2018


version tests dependencies coverage chat

A modern static build tool, powered by webpack

No Maintenance Intended

Note: This project is currently unmaintained. If you are interested in taking over maintenance, please reach out!

What is Spike?

We ❤️ static.

If you're building a website or client-side app – then 🌵 spike is probably for you. Spike aims to be simple, efficient, and a pleasure to use.

Spike certainly is not the only static site generator out there, but in our opinion, it's the most powerful and easiest to use.

Spike's default stack is built on plugin-based architecture which defaults to syntax based on official specs for the future of html, css, and javascript. Out of the box, Spike is based on:

It is also able to integrate any webpack loader and plugin, making it possible to use any other language and configuration you want.



  • npm install spike -g
  • spike new <projectname>

NOTE: You must be using >= node v6.0.0 in order for Spike to work!


Spike can operate through either a javascript API or a CLI interface. This project is just the command line interface, for more information on the js api, check out spike-core.

To read all about how spike works, check out our documentation

For information on how to use the command line interface, check the CLI section


In order to continue improving Spike, we collect anonymous usage data from anyone using the command line tool. This data is important to us because it helps us to know which features are important to users. It also helps us to convince our sponsors about how great this project is and how many people are relying on it, so that its development can continue to be funded. Here's a breakdown of the data we collect:

  • A randomly generated unique id for each spike install
  • Any time a spike command is run, the contents of that command (for example spike watch -e production would record "watch -e production")
  • Any time a spike site is compiled, only the fact that a compile has run

We use this data specifically to keep tabs on how frequently spike's various features are being used so that we can better prioritize issues and upgrades, and to show our "total compiles" number, which is typically a large and impressive number, to our sponsors, and they can then be wowed by how awesome and popular this project is. That's it!

We want to make it clear that no private information is being collected at all here, and that all information collected is 100% anonymous, and tagged only to an entirely randomly generated id. However, if you would like to opt-out and ensure that analytics are not sent, you can run spike analytics disable, and no further information will be collected.

You can’t perform that action at this time.