Package Exports

warning

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 (warning) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Warning

A mirror of Facebook's Warning

Usage

npm install warning

// some script
var warning = require('warning');

var ShouldBeTrue = false;

warning(ShouldBeTrue, 'This thing should be true but you set to false. No soup
for you!');
//  'This thing should be true but you set to false. No soup for you!'

Similar to Facebook's invariant but only logs a warning if the condition is not met. This can be used to log issues in development environments in critical paths. Removing the logging code for production environments will keep the same logic and follow the same code paths.

Browserify

When using browserify, the browser.js file will be imported instead of invariant.js and browserify will be told to transform the file with envify. The only difference between browser.js and invariant.js is the process.env.NODE_ENV variable isn't cached. This, in combination with envify and (optionally) uglifyjs, will result in a noop in production environments. Otherwise behavior is as expected.

Don't Forget To Be Awesome