Use own version of React component traversal module

The original version of react-traverse was not built with ES5 as a target and its build process was out of date.

Pulled in the relevant code of the module and used our own set of dependencies + a webpack build to make it work with our setup

2.0.0: Refactor/maintain functionality with malformed configuration (#4)

• Modifies the way errors are handled at library level
• Changes the screenName config option to identifier for clarity

First version

Fix/enable npm installation (#3)

* chore: Move main entryopint to `lib/`

Signed-off-by: Adrian Oprea <[email protected]>

* feat: Enable webpack builds

Signed-off-by: Adrian Oprea <[email protected]>

* refactor(enhanceComponent): Remove extra path prefix

This small hack tricks the WEbpack sourcemap plugin into bypassing its
memory leak.

Signed-off-by: Adrian Oprea <[email protected]>

* refactor(getScreenConfig): Use the globla configuration module

Signed-off-by: Adrian Oprea <[email protected]>

* feat: Add dynamic configuration module

Signed-off-by: Adrian Oprea <[email protected]>

* chore: Add dependencies

Signed-off-by: Adrian Oprea <[email protected]>

* chore: Add build to repo

Until we publish to npm, this is going to be necessary

Signed-off-by: Adrian Oprea <[email protected]>

* refactor(isClass): Return true boolean

The verification would return the `isReactComponent` property value instead of true or false. This would later be evaluated to its boolean value in the if statements

* refactor(enhanceTreeStructureWithExtras): Reuse code for components and dom elements

*  refactor(enhanceComponent):Add external loader function

Webpack is unable to resolve the module paths if the loading is declared inside the module itself.

* refactor(enhanceComponent): Pipe the component configuration directly through

* refactor: Remove library configuration

The module was performing serialization which was useless for path
resolution in Webpack

Signed-off-by: Adrian Oprea <[email protected]>

* refactor(getScreenConfig): Work directly on the configuration object

Signed-off-by: Adrian Oprea <[email protected]>

* feat(createLoader): Add utility function for loader creation

The function abstracts the loader creation mechanism and allows the
passing of the import functionality. This is hacky but is required by
Webpack to resolve the paths to our addons properly.

Signed-off-by: Adrian Oprea <[email protected]>

* refactor(withExtras): Pass the configuration object directly through

Signed-off-by: Adrian Oprea <[email protected]>

* chore(dist): Update module build

Signed-off-by: Adrian Oprea <[email protected]>