Package Exports

now
now/build/lib
now/build/lib/alias
now/package.json

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (now) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

𝚫 now

The fastest way to deploy a Node.JS service.

How it works

In any directory with a package.json, run:

$ now
> https://some-code-nd23n2.now.sh

every time you run it, you get a new URL (unless nothing's changed).

Conventions

package.json must contain a start task inside scripts. If a now script is defined, that's used instead.
Only files that would be included in npm publish are synchronized. package.json files field, .npmignore and .gitignore are supported.
If a build step is needed, specify a build task in scripts. If now-build is defined, that's used instead.

Installing

$ npm install -g now
> Enter your email: rauchg@gmail.com.
> We sent an email. Click to log in.

Features

Slim. No reliance on Git.
Fast. Blazing fast sync with deduping.
Standard. Respects npm and Node.JS conventions.
Easy. No need to specify ports, Dockerfile or config.

Options

-d  Debug mode. Lists all files to be uploaded.
-f  Force. Creates a new URL even if nothing has changed.