rsms

export class EventEmitter<Events, K = keyof Events|symbol> {
  addListener(event: K, listener: (...args: any[]) => void): this;
  on(event: K, listener: (...args: any[]) => void): this;
  once(event: K, listener: (...args: any[]) => void): this;
  removeListener(event: K, listener: (...args: any[]) => void): this;
  removeAllListeners(event?: K): this;
  setMaxListeners(n: number): this;
  getMaxListeners(): number;
  listeners(event: K): Function[];
  emit(event: K, ...args: any[]): boolean;

Aldredcz

Notes

• This code handles any JS runtime error during rendering React components. Without this handling, once an error occurs, whole component tree is damaged and can't be used at all. With this handling, nothing will be rendered in production environment (error span in dev env.) + in production the error is logged to Sentry (if you are not using it just delete related code)
• This is basicaly a workaround for proposed feature in React core - described in Issue: facebook/react#2461
• Works for all variants of Component creation - React.createClass, extending React.Component and also stateless functional components.
• To get this work, just put this snippet into your entry js file. Then it will work in whole application.
• Also supporting React Hot Reload!
• If you find this useful, please retweet https://twitter.com/Aldredcz/status/744650159942995968 :)

Ideas

• specify custom error renderer (global / per component, e.g. by implementing method renderOnError() in a comp

jlong

var parser = document.createElement('a');
parser.href = "http://example.com:3000/pathname/?search=test#hash";

parser.protocol; // => "http:"
parser.hostname; // => "example.com"
parser.port;     // => "3000"
parser.pathname; // => "/pathname/"
parser.search;   // => "?search=test"
parser.hash;     // => "#hash"
parser.host;     // => "example.com:3000"