History

Matt Ellis d7575072f2 Do not use relative path when launching dynamic provider Previously, we assumed that the dynamic provider was located in `./node_modules/@pulumi/pulumi/../` which is correct in the majority of cases. However, tools like lerna or yarn workspaces (or custom workflows) allow the node_modules folder to be located elsewhere on disk, and node will still find it because of its algorithm for module resolution. So, do what we do in the language host itself, first launch node and ask it to tell us where it resolves a require statement to on disk and then launch node against that script. Fixes #2261		2018-12-05 13:45:06 -08:00
..
asset	Make RTTI markers internal (#1479 )	2018-06-07 21:34:06 -07:00
cmd	Flush stdout and stderr on abnormal lang shutdown (#2226 )	2018-11-19 17:59:01 -05:00
dist	Do not use relative path when launching dynamic provider	2018-12-05 13:45:06 -08:00
dynamic	Reimplement refresh. (#1814 )	2018-08-22 17:52:46 -07:00
iterable	Add an extra layer of Input-ness	2018-10-27 13:47:15 -07:00
log	Expose hte ephemeral logging flag to the Nodejs sdk. (#2056 )	2018-10-12 11:09:09 -07:00
proto	Move management of root resource state to engine (#1944 )	2018-09-18 11:47:34 -07:00
runtime	make the context-param non-optional for debuggable promises. (#2242 )	2018-11-24 18:57:17 -08:00
tests	Inherit custom resource providers (#2264 )	2018-12-05 12:35:19 -08:00
.gitignore	Continue to add native modules to NODE_PATH	2018-04-13 14:26:32 -07:00
Makefile	Pass -count=1 to disable result caching on go 1.10 and above	2018-11-08 14:11:52 -08:00
README.md	Remove Private Beta warning	2018-06-18 05:00:38 -07:00
config.ts	Fix requireObject docs (#1961 )	2018-09-21 07:58:14 -07:00
errors.ts	Fix rtti check. (#1983 )	2018-09-24 20:06:31 -07:00
index.ts	Add an API for importing stack outputs (#2180 )	2018-11-14 13:33:35 -08:00
invoke.ts	Pull default options from a resource's parent. (#1748 )	2018-08-10 16:18:21 -07:00
metadata.ts	Add license headers	2018-05-22 15:02:47 -07:00
package.json	Bump @types/node dependency	2018-11-13 11:20:21 -08:00
resource.ts	Inherit custom resource providers (#2264 )	2018-12-05 12:35:19 -08:00
stackReference.ts	Add an API for importing stack outputs (#2180 )	2018-11-14 13:33:35 -08:00
tsconfig.json	Add stackReference.ts to tsconfig.json (#2253 )	2018-11-29 10:27:29 -08:00
tslint.json	Add license headers	2018-05-22 15:02:47 -07:00
version.ts	Add license headers	2018-05-22 15:02:47 -07:00

README.md

Pulumi Node.js SDK

The Pulumi Node.js SDK lets you write cloud programs in JavaScript.

Installation

Using npm:

$ npm install --save @pulumi/pulumi

Using yarn:

$ yarn add @pulumi/pulumi

This SDK is meant for use with the Pulumi CLI. Please visit pulumi.io for installation instructions.

Building and Testing

For anybody who wants to build from source, here is how you do it.

Prerequisites

This SDK uses Node.js and we support the Active LTS and Current releases, as defined by this table. We support both NPM and Yarn for package management.

At the moment, we only support building on macOS and Linux, where standard GNU tools like make are available.

Make Targets

The first time you build, run make ensure to install and prepare native plugins for V8:

$ make ensure

This is only necessary if you intend to produce a build that is capable of running older versions of the SDK contained in this directory. If you do intend to do this, you must have node 6.10.2 installed.

To build the SDK, simply run make from the root directory (where this README lives, at sdk/nodejs/ from the repo's root). This will build the code, run tests, and install the package and its supporting artifacts.

At the moment, for local development, we install everything into /opt/pulumi. You will want this on your $PATH.

The tests will verify that everything works, but feel free to try running pulumi preview and/or pulumi update from the examples/minimal/ directory. Remember to run tsc first, since pulumi expects JavaScript, not TypeScript.