Amjad Masad 289989dc3f Error on name collisions ... Summary: @​public This moves us from warnings on name collisions to errors. If the error happens in initialization it will fatal out. However, if the error happens while working (after initialization) then I did my best to make it recoverable. The rational behind this is that if you're working and you're changing names, you may introduce a duplication while moving things around. It will suck if you have to restart the server every time you do that. Reviewed By: @frantic Differential Revision: D2493098		2015-09-30 21:02:50 -07:00
..
Activity	Simplify over-engineered Activity module	2015-09-22 14:25:37 -07:00
AssetServer	Return concrete file paths to the client	2015-09-22 15:45:25 -07:00
Bundler	Introduce `getOrderedDependencyPaths` that gets all concrete dependecy paths	2015-09-29 18:34:21 -07:00
BundlesLayout	Simplify over-engineered Activity module	2015-09-22 14:25:37 -07:00
Cache	Fix tests + enable inline requires on react-native	2015-09-21 14:39:44 -07:00
DependencyResolver	Error on name collisions	2015-09-30 21:02:50 -07:00
FileWatcher	Fix tests + enable inline requires on react-native	2015-09-21 14:39:44 -07:00
JSTransformer	Fix debug namespaces	2015-09-29 16:10:22 -07:00
Server	Introduce `getOrderedDependencyPaths` that gets all concrete dependecy paths	2015-09-29 18:34:21 -07:00
SocketInterface	Introduce `getOrderedDependencyPaths` that gets all concrete dependecy paths	2015-09-29 18:34:21 -07:00
__mocks__	[react-packager] Make the fs mock async	2015-08-19 17:17:15 -07:00
lib	Revert packager randomization revert	2015-09-25 10:24:06 -07:00
transforms/babel-plugin-system-import	[react-packager] `System.import` transform	2015-08-27 09:28:48 -08:00