Jason Strimpel jstrimpel

Widget instances should have an event aggregator.

Triggering Events

Signature is eventName and data.

Listening for Events

Signature is eventName and callback that receives data from event trigger.

`addChild(container, component, options)`

Add a child component to a parent's container.

Arguments

container (String): Component container to which the child will be added.
component (String): Component to be added.
options (Object):
- success (Function): Success callback.
- error (Function): Error callback.
- index (Number): Insert index for the container. The default is 0.

Capture analytics from synthetic events and gather performance metrics
Transform React components

I have two modules A and B. A declares B as a dependency. B is built into a bundle and B's bundle is used as an entry for a DllPlugin bundle. A's build uses the manifest generated by B in a DllReferencePlugin config. I cannot get A's build to externalize and reference B's DLL. Below are the plugin configurations.

A

new webpack.DllReferencePlugin({
  context: 'ABSOLUTE_PATH_TO_B',
  manifest: require('ABSOLUTE_PATH_TO_B/dist/index-manifest')
})

Is it possible to have separate build processes that generate bundles that define dependencies, which can be used by an application without having to expose globals and rely on aliases?

Requirement

There are two separate build processes:

Core: This builds a distribution of common core dependencies
Component: This externalizes anything in core build

Use Case

The following two files are entry points for two different build processes. The component entry webpack config defines core as an external.

	define(['lazoServer'], function (LazoServer) {

	'use strict';

	return LazoServer.extend({
	// register good with lazo server pack
	// hapi - a reference to the hapi module itself
	// pack - the lazo server pack
	// servers - the servers that belong to the lazo pack
	// options.success and options.error

	React.config({
	HTMLDOMPropertyConfig: {
	isCustomAttribute: RegExp.prototype.test.bind(/^(data\|aria\|lazo)-[a-z_][a-z\d_.\-]*$/),
	Properties: {
	'some-other-prop': null
	}
	});

	// would trigger ReactInjection.DOMProperty.injectDOMPropertyConfig(HTMLDOMPropertyConfig);

	var Hapi = require('hapi');

	// Create a server with a host and port
	var server = new Hapi.Server();
	server.connection({
	host: 'localhost',
	port: 8000
	});

	// Add the route

	// this outlines the recommended approach for handling code samples in the book
	// block 1 introdcues a stubbed module
	// block 2 contains implementation details for subbed module method
	// this prevents duplication while still providing context
	// comments before code block would be the code block tile in the book

	// [[app_stub_2_4]]
	// Application Stub
	export default class Application {

	define(['loader!request'], function (someModule) {

	});