Greg Bergé 10318b042e fix: fix module resolving ...

This issue fixes #59

It is possible to create a configuration which will result into a wrong state but it should not happen in 99.99% cases.

2018-05-12 16:09:44 +02:00

..

__fixtures__

feat: attach static properties on load

2018-04-05 23:27:05 +02:00

server

docs: improve error message (#75)

2018-05-08 22:51:31 +02:00

utils

feat: ship a single js file

2018-02-04 16:26:53 +01:00

babel.js

feat: stable version 1

2018-02-02 15:24:21 +01:00

babel.test.js

feat: stable version 1

2018-02-02 15:24:21 +01:00

componentTracker.js

fix: fix module resolving

2018-05-12 16:09:44 +02:00

componentTracker.test.js

fix: fix module resolving

2018-05-12 16:09:44 +02:00

constants.js

feat: ship a single js file

2018-02-04 16:26:53 +01:00

getState.js

fix(snapshot): fix snap usage

2018-02-06 10:27:08 +01:00

getState.test.js

fix(snapshot): fix snap usage

2018-02-06 10:27:08 +01:00

index.js

refactor: remove HMR relative code

2018-05-05 21:33:06 +02:00

loadable.js

refactor: remove HMR relative code

2018-05-05 21:33:06 +02:00

loadable.test.js

fix: set correct loading state if component is already loaded. (#64)

2018-04-18 17:27:26 +02:00

loadComponents.js

fix: state could have no children

2018-02-04 10:43:05 +01:00

loadComponents.test.js

fix: state could have no children

2018-02-04 10:43:05 +01:00