CLI for the CDN
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
lib updates project output Apr 21, 2018
test updates tests Apr 21, 2018
.gitignore Adds npm debug files to git ignore Sep 8, 2015
.travis.yml Adds CI for OS X Sep 28, 2015 resets ssl flow Feb 14, 2018
appveyor.yml Adds CI for Windows Sep 28, 2015
package-lock.json updates tests Apr 21, 2018
package.json removes deprecated libs Mar 2, 2018


Publish web apps to a CDN with a single command and no setup required.


This is the CLI client for the hosted service. It’s what gets installed when you run npm install -g surge.

This CLI library manages access tokens locally and handles the upload and subsequent reporting when you publish a project using surge.


It’s easier to show than tell so let’s get to it! The following command will deploy the current working directory to the surge servers where the application will be available at

$ surge ./

Run surge --help to see the following overview of the surge command...

  Surge – Single-command web publishing. (v0.17.6)

    surge [options]

    -p, --project       path to projects asset directory (./)
    -d, --domain        domain of your project (<random>
    -a, --add           adds user to list of collaborators (email address)
    -r, --remove        removes user from list of collaborators (email address)
    -V, --version       show the version number
    -h, --help          show this help message

  Shorthand usage:
    surge [project] [domain]

  Additional commands:
    surge whoami        show who you are logged in as
    surge logout        expire local token
    surge login         only performs authentication step
    surge list          list all domains you have access to
    surge teardown      tear down a published project

    Getting started
    Custom domains
    Additional help

  When in doubt, run surge from within your project directory.

CDN Features

  • Custom CNAME & custom SSL
  • Fallback 404.html pages
  • HTML5 mode 200.html pages
  • Stays out of gits way
  • Supports clean URLs && trailing slashes /
  • Implicit signup
  • Supports CNAME files

If you’re using tools like Grunt, Gulp, or a static site generator like Jekyll, your files are output into a compile directory like _site/, build/, or www/. From the root of your project, pass Surge the path to this directory to upload your compiled assets.

surge www

You may also add this directory to your .gitignore to keep your compiled assets out of your Git history.