Sergii Stotskyi

Anyway, ideally I need to add a check with the proper error message, so users are no confused. That's why I reopen this issue

I’ll check today whether access to rootSuite really necessary

I finally understood why it throws. The issue is in new `jest-circus` package. This is a test runner that is going to replace jest starting from v27. And it looks...

 This is a screenshot of package.json after `react-scripts eject` command in the project described in [this comment](https://github.com/stalniy/bdd-lazy-var/issues/97#issuecomment-717665083)

There is very little information about jest-circus and its internals, so it will take some time to create/adapt integration for it

So, the workaround is too switch back `jest-jasmine2` runner, however I don't know whether it's possible to change jest config without ejection. **Update**: to do this - `npm install jest-jasmine2`...

I have some thoughts on how to improves typescript integration and this may change how variables are created and integrated with testing framework. Something like this ```ts import { lazy...

However the issue with this approach is that for every nested describe we need a separate variable but we can't use the same name every time. So, the only way...

Would it be better to have a convention like `$`, `$1`, `$2`, ... where number after $ means a nesting level. Usually it shouldn’t go deeper $2. ```ts import {...

No updates. What interface do you use, bad-lazy-var/global?