1.0.1

blah# React ·

React is a JavaScript library for building user interfaces.

• Declarative: React makes it painless to create interactive UIs. Design simple views for each state in your application, and React will efficiently update and render just the right components when your data changes. Declarative views make your code more predictable, simpler to understand, and easier to debug.
• Component-Based: Build encapsulated components that manage their own state, then compose them to make complex UIs. Since component logic is written in JavaScript instead of templates, you can easily pass rich data through your app and keep state out of the DOM.
• Learn Once, Write Anywhere: We don't make assumptions about the rest of your technology stack, so you can develop new features in React without rewriting existing code. React can also render on the server using Node and power mobile apps using React Native.

Learn how to use React in your own project.

Installation

React has been designed for gradual adoption from the start, and you can use as little or as much React as you need:

• Use Online Playgrounds to get a taste of React.
• Add React to a Website as a <script> tag in one minute.
• Create a New React App if you're looking for a powerful JavaScript toolchain.

You can use React as a <script> tag from a CDN, or as a react package on npm.

Documentation

You can find the React documentation on the website.

Check out the Getting Started page for a quick overview.

The documentation is divided into several sections:

• Tutorial
• Main Concepts
• Advanced Guides
• API Reference
• Where to Get Support
• Contributing Guide

You can improve it by sending pull requests to this repository.

Examples

We have several examples on the website. Here is the first one to get you started:

function HelloMessage({ name }) {
  return <div>Hello {name}</div>;
}

ReactDOM.render(
  <HelloMessage name="Taylor" />,
  document.getElementById('container')
);

This example will render "Hello Taylor" into a container on the page.

You'll notice that we used an HTML-like syntax; we call it JSX. JSX is not required to use React, but it makes code more readable, and writing it feels like writing HTML. If you're using React as a <script> tag, read this section on integrating JSX; otherwise, the recommended JavaScript toolchains handle it automatically.

Contributing

The main purpose of this repository is to continue to evolve React core, making it faster and easier to use. Development of React happens in the open on GitHub, and we are grateful to the community for contributing bugfixes and improvements. Read below to learn how you can take part in improving React.

Code of Conduct

Facebook has adopted a Code of Conduct that we expect project participants to adhere to. Please read the full text so that you can understand what actions will and will not be tolerated.

Contributing Guide

Read our contributing guide to learn about our development process, how to propose bugfixes and improvements, and how to build and test your changes to React.

Good First Issues

To help you get your feet wet and get you familiar with our contribution process, we have a list of good first issues that contain bugs which have a relatively limited scope. This is a great place to get started.

License

React is MIT licensed.

1.0.0

React ·

React is a JavaScript library for building user interfaces.

• Declarative: React makes it painless to create interactive UIs. Design simple views for each state in your application, and React will efficiently update and render just the right components when your data changes. Declarative views make your code more predictable, simpler to understand, and easier to debug.
• Component-Based: Build encapsulated components that manage their own state, then compose them to make complex UIs. Since component logic is written in JavaScript instead of templates, you can easily pass rich data through your app and keep state out of the DOM.
• Learn Once, Write Anywhere: We don't make assumptions about the rest of your technology stack, so you can develop new features in React without rewriting existing code. React can also render on the server using Node and power mobile apps using React Native.

Learn how to use React in your own project.

Installation

React has been designed for gradual adoption from the start, and you can use as little or as much React as you need:

• Use Online Playgrounds to get a taste of React.
• Add React to a Website as a <script> tag in one minute.
• Create a New React App if you're looking for a powerful JavaScript toolchain.

You can use React as a <script> tag from a CDN, or as a react package on npm.

Documentation

You can find the React documentation on the website.

Check out the Getting Started page for a quick overview.

The documentation is divided into several sections:

• Tutorial
• Main Concepts
• Advanced Guides
• API Reference
• Where to Get Support
• Contributing Guide

You can improve it by sending pull requests to this repository.

Examples

We have several examples on the website. Here is the first one to get you started:

function HelloMessage({ name }) {
  return <div>Hello {name}</div>;
}

ReactDOM.render(
  <HelloMessage name="Taylor" />,
  document.getElementById('container')
);

This example will render "Hello Taylor" into a container on the page.

You'll notice that we used an HTML-like syntax; we call it JSX. JSX is not required to use React, but it makes code more readable, and writing it feels like writing HTML. If you're using React as a <script> tag, read this section on integrating JSX; otherwise, the recommended JavaScript toolchains handle it automatically.

Contributing

The main purpose of this repository is to continue to evolve React core, making it faster and easier to use. Development of React happens in the open on GitHub, and we are grateful to the community for contributing bugfixes and improvements. Read below to learn how you can take part in improving React.

Code of Conduct

Facebook has adopted a Code of Conduct that we expect project participants to adhere to. Please read the full text so that you can understand what actions will and will not be tolerated.

Contributing Guide

Read our contributing guide to learn about our development process, how to propose bugfixes and improvements, and how to build and test your changes to React.

Good First Issues

To help you get your feet wet and get you familiar with our contribution process, we have a list of good first issues that contain bugs which have a relatively limited scope. This is a great place to get started.

License

React is MIT licensed.

0.1.2

pkgcloud

WE HAVE A NEWER VERSION.

pkgcloud is a standard library for node.js that abstracts away differences among multiple cloud providers.

• Getting started
  • Basic APIs
  • Unified Vocabulary
  • Supported APIs
• Compute
• Storage
  • Uploading Files
  • Downloading Files
• Database
• DNS (beta)
• Block Storage (beta)
• Load Balancers (beta)
• Orchestration (beta)
• Network (beta)
• CDN (beta)
• Fine Print
  • Installation
  • Tests
  • Logging
  • Code Coverage
  • Contribute!
  • Roadmap

Getting Started

You can install pkgcloud via npm or add to it to dependencies in your package.json file:

npm install pkgcloud

Currently there are nine service types which are handled by pkgcloud:

• Compute
• Storage
• Database
• DNS (beta)
• Block Storage (beta)
• Load Balancers (beta)
• Network (beta)
• Orchestration (beta)
• CDN (beta)

In our Roadmap, we plan to add support for more services, such as Queueing, Monitoring, and more. Additionally, we plan to implement more providers for the beta services, thus moving them out of beta.

User Agent

By default, all pkgcloud HTTP requests will have a user agent with the library and version: nodejs-pkgcloud/x.y.z where x.y.z is the current version.

You can get this from a client at any time by calling client.getUserAgent();. Some providers may have an additional suffix as a function of the underlying HTTP stacks.

You can also set a custom User Agent prefix:

client.setCustomUserAgent('my-app/1.2.3');

// returns "my-app/1.2.3 nodejs-pkgcloud/1.1.0"
client.getUserAgent();

Basic APIs for pkgcloud

Services provided by pkgcloud are exposed in two ways:

• By service type: For example, if you wanted to create an API client to communicate with a compute service you could simply:

  var client = require('pkgcloud').compute.createClient({
    //
    // The name of the provider (e.g. "joyent")
    //
    provider: 'provider-name',

    //
    // ... Provider specific credentials
    //
  });

• By provider name: For example, if you knew the name of the provider you wished to communicate with you could do so directly:

  var client = require('pkgcloud').providers.joyent.compute.createClient({
    //
    // ... Provider specific credentials
    //
  });

All API clients exposed by pkgcloud can be instantiated through pkgcloud[serviceType].createClient({ ... }) or pkcloud.providers[provider][serviceType].createClient({ ... }).

Unified Vocabulary

Due to the differences between the vocabulary for each service provider, pkgcloud uses its own unified vocabulary.

• Compute: Server, Image, Flavor
• Storage: Container, File
• DNS: Zone, Record

Note: Unified vocabularies may not yet be defined for beta services.

Supported APIs

Supporting every API for every cloud service provider in Node.js is a huge undertaking, but that is the long-term goal of pkgcloud. Special attention has been made to ensure that each service type has enough providers for a critical mass of portability between providers (i.e. Each service implemented has multiple providers).

If a service does not have at least two providers, it is considered a beta interface; We reserve the right to improve the API as multiple providers will allow generalization to be better determined.

• Compute
  • Amazon
  • Azure
  • DigitalOcean
  • HP
  • Joyent
  • Openstack
  • Rackspace
• Storage
  • Amazon
  • Azure
  • Google
  • HP
  • Openstack
  • Rackspace
• Database
  • IrisCouch
  • MongoLab
  • Rackspace
  • MongoHQ
  • RedisToGo
• DNS (beta)
  • Rackspace
• Block Storage (beta)
  • Rackspace
  • Openstack
• Load Balancers (beta)
  • Rackspace
• Orchestration (beta)
  • Openstack
  • Rackspace
• Network (beta)
  • HP
  • Openstack
  • Rackspace
• CDN (beta)
  • Openstack
  • Rackspace

Compute

The pkgcloud.compute service is designed to make it easy to provision and work with VMs. To get started with a pkgcloud.compute client just create one:

  var client = require('pkgcloud').compute.createClient({
    //
    // The name of the provider (e.g. "joyent")
    //
    provider: 'provider-name',

    //
    // ... Provider specific credentials
    //
  });

Each compute provider takes different credentials to authenticate; these details about each specific provider can be found below:

• Amazon
• Azure
• DigitalOcean
• HP
• Joyent
• Openstack
• Rackspace

Each instance of pkgcloud.compute.Client returned from pkgcloud.compute.createClient has a set of uniform APIs:

Server

• client.getServers(function (err, servers) { })
• client.createServer(options, function (err, server) { })
• client.destroyServer(serverId, function (err, server) { })
• client.getServer(serverId, function (err, server) { })
• client.rebootServer(server, function (err, server) { })

Image

• client.getImages(function (err, images) { })
• client.getImage(imageId, function (err, image) { })
• client.destroyImage(image, function (err, ok) { })
• client.createImage(options, function (err, image) { })

Flavor

• client.getFlavors(function (err, flavors) { })
• client.getFlavor(flavorId, function (err, flavor) { })

Storage

The pkgcloud.storage service is designed to make it easy to upload and download files to various infrastructure providers. Special attention has been paid so that methods are streams and pipe-capable.

To get started with a pkgcloud.storage client just create one:

  var client = require('pkgcloud').storage.createClient({
    //
    // The name of the provider (e.g. "joyent")
    //
    provider: 'provider-name',

    //
    // ... Provider specific credentials
    //
  });

Each storage provider takes different credentials to authenticate; these details about each specific provider can be found below:

• Amazon
• Azure
• Google
• HP
• Openstack
• Rackspace

Each instance of pkgcloud.storage.Client returned from pkgcloud.storage.createClient has a set of uniform APIs:

Container

• client.getContainers(function (err, containers) { })
• client.createContainer(options, function (err, container) { })
• client.destroyContainer(containerName, function (err) { })
• client.getContainer(containerName, function (err, container) { })

File

• client.upload(options)
• client.download(options, function (err) { })
• client.getFiles(container, function (err, files) { })
• client.getFile(container, file, function (err, server) { })
• client.removeFile(container, file, function (err) { })

Both the .upload(options) and .download(options) have had careful attention paid to make sure they are pipe and stream capable:

Upload a File

  var pkgcloud = require('pkgcloud'),
      fs = require('fs');

  var client = pkgcloud.storage.createClient({ /* ... *...

0.1.1

pkgcloud

WE HAVE A NEWER VERSION.

pkgcloud is a standard library for node.js that abstracts away differences among multiple cloud providers.

• Getting started
  • Basic APIs
  • Unified Vocabulary
  • Supported APIs
• Compute
• Storage
  • Uploading Files
  • Downloading Files
• Database
• DNS (beta)
• Block Storage (beta)
• Load Balancers (beta)
• Orchestration (beta)
• Network (beta)
• CDN (beta)
• Fine Print
  • Installation
  • Tests
  • Logging
  • Code Coverage
  • Contribute!
  • Roadmap

Getting Started

You can install pkgcloud via npm or add to it to dependencies in your package.json file:

npm install pkgcloud

Currently there are nine service types which are handled by pkgcloud:

• Compute
• Storage
• Database
• DNS (beta)
• Block Storage (beta)
• Load Balancers (beta)
• Network (beta)
• Orchestration (beta)
• CDN (beta)

In our Roadmap, we plan to add support for more services, such as Queueing, Monitoring, and more. Additionally, we plan to implement more providers for the beta services, thus moving them out of beta.

User Agent

By default, all pkgcloud HTTP requests will have a user agent with the library and version: nodejs-pkgcloud/x.y.z where x.y.z is the current version.

You can get this from a client at any time by calling client.getUserAgent();. Some providers may have an additional suffix as a function of the underlying HTTP stacks.

You can also set a custom User Agent prefix:

client.setCustomUserAgent('my-app/1.2.3');

// returns "my-app/1.2.3 nodejs-pkgcloud/1.1.0"
client.getUserAgent();

Basic APIs for pkgcloud

Services provided by pkgcloud are exposed in two ways:

• By service type: For example, if you wanted to create an API client to communicate with a compute service you could simply:

  var client = require('pkgcloud').compute.createClient({
    //
    // The name of the provider (e.g. "joyent")
    //
    provider: 'provider-name',

    //
    // ... Provider specific credentials
    //
  });

• By provider name: For example, if you knew the name of the provider you wished to communicate with you could do so directly:

  var client = require('pkgcloud').providers.joyent.compute.createClient({
    //
    // ... Provider specific credentials
    //
  });

All API clients exposed by pkgcloud can be instantiated through pkgcloud[serviceType].createClient({ ... }) or pkcloud.providers[provider][serviceType].createClient({ ... }).

Unified Vocabulary

Due to the differences between the vocabulary for each service provider, pkgcloud uses its own unified vocabulary.

• Compute: Server, Image, Flavor
• Storage: Container, File
• DNS: Zone, Record

Note: Unified vocabularies may not yet be defined for beta services.

Supported APIs

Supporting every API for every cloud service provider in Node.js is a huge undertaking, but that is the long-term goal of pkgcloud. Special attention has been made to ensure that each service type has enough providers for a critical mass of portability between providers (i.e. Each service implemented has multiple providers).

If a service does not have at least two providers, it is considered a beta interface; We reserve the right to improve the API as multiple providers will allow generalization to be better determined.

• Compute
  • Amazon
  • Azure
  • DigitalOcean
  • HP
  • Joyent
  • Openstack
  • Rackspace
• Storage
  • Amazon
  • Azure
  • Google
  • HP
  • Openstack
  • Rackspace
• Database
  • IrisCouch
  • MongoLab
  • Rackspace
  • MongoHQ
  • RedisToGo
• DNS (beta)
  • Rackspace
• Block Storage (beta)
  • Rackspace
  • Openstack
• Load Balancers (beta)
  • Rackspace
• Orchestration (beta)
  • Openstack
  • Rackspace
• Network (beta)
  • HP
  • Openstack
  • Rackspace
• CDN (beta)
  • Openstack
  • Rackspace

Compute

The pkgcloud.compute service is designed to make it easy to provision and work with VMs. To get started with a pkgcloud.compute client just create one:

  var client = require('pkgcloud').compute.createClient({
    //
    // The name of the provider (e.g. "joyent")
    //
    provider: 'provider-name',

    //
    // ... Provider specific credentials
    //
  });

Each compute provider takes different credentials to authenticate; these details about each specific provider can be found below:

• Amazon
• Azure
• DigitalOcean
• HP
• Joyent
• Openstack
• Rackspace

Each instance of pkgcloud.compute.Client returned from pkgcloud.compute.createClient has a set of uniform APIs:

Server

• client.getServers(function (err, servers) { })
• client.createServer(options, function (err, server) { })
• client.destroyServer(serverId, function (err, server) { })
• client.getServer(serverId, function (err, server) { })
• client.rebootServer(server, function (err, server) { })

Image

• client.getImages(function (err, images) { })
• client.getImage(imageId, function (err, image) { })
• client.destroyImage(image, function (err, ok) { })
• client.createImage(options, function (err, image) { })

Flavor

• client.getFlavors(function (err, flavors) { })
• client.getFlavor(flavorId, function (err, flavor) { })

Storage

The pkgcloud.storage service is designed to make it easy to upload and download files to various infrastructure providers. Special attention has been paid so that methods are streams and pipe-capable.

To get started with a pkgcloud.storage client just create one:

  var client = require('pkgcloud').storage.createClient({
    //
    // The name of the provider (e.g. "joyent")
    //
    provider: 'provider-name',

    //
    // ... Provider specific credentials
    //
  });

Each storage provider takes different credentials to authenticate; these details about each specific provider can be found below:

• Amazon
• Azure
• Google
• HP
• Openstack
• Rackspace

Each instance of pkgcloud.storage.Client returned from pkgcloud.storage.createClient has a set of uniform APIs:

Container

• client.getContainers(function (err, containers) { })
• client.createContainer(options, function (err, container) { })
• client.destroyContainer(containerName, function (err) { })
• client.getContainer(containerName, function (err, container) { })

File

• client.upload(options)
• client.download(options, function (err) { })
• client.getFiles(container, function (err, files) { })
• client.getFile(container, file, function (err, server) { })
• client.removeFile(container, file, function (err) { })

Both the .upload(options) and .download(options) have had careful attention paid to make sure they are pipe and stream capable:

Upload a File

  var pkgcloud = require('pkgcloud'),
      fs = require('fs');

  var client = pkgcloud.storage.createClient({ /* ... *...

0.1.0

pkgcloud

WE HAVE A NEWER VERSION.

pkgcloud is a standard library for node.js that abstracts away differences among multiple cloud providers.

• Getting started
  • Basic APIs
  • Unified Vocabulary
  • Supported APIs
• Compute
• Storage
  • Uploading Files
  • Downloading Files
• Database
• DNS (beta)
• Block Storage (beta)
• Load Balancers (beta)
• Orchestration (beta)
• Network (beta)
• CDN (beta)
• Fine Print
  • Installation
  • Tests
  • Logging
  • Code Coverage
  • Contribute!
  • Roadmap

Getting Started

You can install pkgcloud via npm or add to it to dependencies in your package.json file:

npm install pkgcloud

Currently there are nine service types which are handled by pkgcloud:

• Compute
• Storage
• Database
• DNS (beta)
• Block Storage (beta)
• Load Balancers (beta)
• Network (beta)
• Orchestration (beta)
• CDN (beta)

In our Roadmap, we plan to add support for more services, such as Queueing, Monitoring, and more. Additionally, we plan to implement more providers for the beta services, thus moving them out of beta.

User Agent

By default, all pkgcloud HTTP requests will have a user agent with the library and version: nodejs-pkgcloud/x.y.z where x.y.z is the current version.

You can get this from a client at any time by calling client.getUserAgent();. Some providers may have an additional suffix as a function of the underlying HTTP stacks.

You can also set a custom User Agent prefix:

client.setCustomUserAgent('my-app/1.2.3');

// returns "my-app/1.2.3 nodejs-pkgcloud/1.1.0"
client.getUserAgent();

Basic APIs for pkgcloud

Services provided by pkgcloud are exposed in two ways:

• By service type: For example, if you wanted to create an API client to communicate with a compute service you could simply:

  var client = require('pkgcloud').compute.createClient({
    //
    // The name of the provider (e.g. "joyent")
    //
    provider: 'provider-name',

    //
    // ... Provider specific credentials
    //
  });

• By provider name: For example, if you knew the name of the provider you wished to communicate with you could do so directly:

  var client = require('pkgcloud').providers.joyent.compute.createClient({
    //
    // ... Provider specific credentials
    //
  });

All API clients exposed by pkgcloud can be instantiated through pkgcloud[serviceType].createClient({ ... }) or pkcloud.providers[provider][serviceType].createClient({ ... }).

Unified Vocabulary

Due to the differences between the vocabulary for each service provider, pkgcloud uses its own unified vocabulary.

• Compute: Server, Image, Flavor
• Storage: Container, File
• DNS: Zone, Record

Note: Unified vocabularies may not yet be defined for beta services.

Supported APIs

Supporting every API for every cloud service provider in Node.js is a huge undertaking, but that is the long-term goal of pkgcloud. Special attention has been made to ensure that each service type has enough providers for a critical mass of portability between providers (i.e. Each service implemented has multiple providers).

If a service does not have at least two providers, it is considered a beta interface; We reserve the right to improve the API as multiple providers will allow generalization to be better determined.

• Compute
  • Amazon
  • Azure
  • DigitalOcean
  • HP
  • Joyent
  • Openstack
  • Rackspace
• Storage
  • Amazon
  • Azure
  • Google
  • HP
  • Openstack
  • Rackspace
• Database
  • IrisCouch
  • MongoLab
  • Rackspace
  • MongoHQ
  • RedisToGo
• DNS (beta)
  • Rackspace
• Block Storage (beta)
  • Rackspace
  • Openstack
• Load Balancers (beta)
  • Rackspace
• Orchestration (beta)
  • Openstack
  • Rackspace
• Network (beta)
  • HP
  • Openstack
  • Rackspace
• CDN (beta)
  • Openstack
  • Rackspace

Compute

The pkgcloud.compute service is designed to make it easy to provision and work with VMs. To get started with a pkgcloud.compute client just create one:

  var client = require('pkgcloud').compute.createClient({
    //
    // The name of the provider (e.g. "joyent")
    //
    provider: 'provider-name',

    //
    // ... Provider specific credentials
    //
  });

Each compute provider takes different credentials to authenticate; these details about each specific provider can be found below:

• Amazon
• Azure
• DigitalOcean
• HP
• Joyent
• Openstack
• Rackspace

Each instance of pkgcloud.compute.Client returned from pkgcloud.compute.createClient has a set of uniform APIs:

Server

• client.getServers(function (err, servers) { })
• client.createServer(options, function (err, server) { })
• client.destroyServer(serverId, function (err, server) { })
• client.getServer(serverId, function (err, server) { })
• client.rebootServer(server, function (err, server) { })

Image

• client.getImages(function (err, images) { })
• client.getImage(imageId, function (err, image) { })
• client.destroyImage(image, function (err, ok) { })
• client.createImage(options, function (err, image) { })

Flavor

• client.getFlavors(function (err, flavors) { })
• client.getFlavor(flavorId, function (err, flavor) { })

Storage

The pkgcloud.storage service is designed to make it easy to upload and download files to various infrastructure providers. Special attention has been paid so that methods are streams and pipe-capable.

To get started with a pkgcloud.storage client just create one:

  var client = require('pkgcloud').storage.createClient({
    //
    // The name of the provider (e.g. "joyent")
    //
    provider: 'provider-name',

    //
    // ... Provider specific credentials
    //
  });

Each storage provider takes different credentials to authenticate; these details about each specific provider can be found below:

• Amazon
• Azure
• Google
• HP
• Openstack
• Rackspace

Each instance of pkgcloud.storage.Client returned from pkgcloud.storage.createClient has a set of uniform APIs:

Container

• client.getContainers(function (err, containers) { })
• client.createContainer(options, function (err, container) { })
• client.destroyContainer(containerName, function (err) { })
• client.getContainer(containerName, function (err, container) { })

File

• client.upload(options)
• client.download(options, function (err) { })
• client.getFiles(container, function (err, files) { })
• client.getFile(container, file, function (err, server) { })
• client.removeFile(container, file, function (err) { })

Both the .upload(options) and .download(options) have had careful attention paid to make sure they are pipe and stream capable:

Upload a File

  var pkgcloud = require('pkgcloud'),
      fs = require('fs');

  var client = pkgcloud.storage.createClient({ /* ... *...