Seth Davenport

Or just do `"ngsticky": "git+https://github.com/d-oliveros/ngSticky.git#v1.8.13",` in `package.json`

seeing the same thing with a React project, sb 6.4.9. In my case I am not using NX

 Searching the code for `initializationPromise` yields no other hits, so I'm not sure where this variable gets set.

Looks from searching the code that something should be calling `globalWindow.__STORYBOOK_STORY_STORE__.resolveInitializationPromise`, but a quick code search turns up no actual calls to this function: https://github.com/storybookjs/storybook/search?q=resolveInitializationPromise

Yeah that's a possibility - I guess the other thing that changed in the given timeframe is we upgraded from jest 26 to jest 27. However our other (non-monorepo) repos...

Thanks for the response - yeah the bundle works etc. so this isn't a blocking issue for me, it just makes the console output hard to read. Unfortunately in this...

So this is looking quite feasible. However I'm waiting for angular/angular-cli#2799 before investing too much time into decorators right now.

My main concerns here are: 1. overlap with the logic behind `configureSubStore` which allows a form of lazy-loaded reducers anyway, and 2. I'm not sure we should tie it directly...

@smithad15 I'm fine with your approach. I'm not going to be refactoring anything any time soon. It's probably not worth the waiting for me since I'm a bit out of...

My concern with this feature is that `'db.customers'` is a perfectly legal property name. What happens if my store looks like this: ```typescript { users: { 'seth.davenport': { age: 35,...