Roderik van Heijst

The behavior of `npm start` was changed a year ago in [this commit](https://github.com/loopbackio/loopback-next/commit/00c9ee71e3b94af36c0a4643a5e91420490ff146), as a fix for [ The application can't start after deleting some model, repository, and controllers ](https://github.com/loopbackio/loopback-next/issues/3259)....

Thanks for getting the investigation on so rapidly and thoroughly! > ``` > The bug is much older than 0x0aNL suggested. I ran into this bug while upgrading the API...

The error we encounter when upgrading the API is: ``` Error: Circular dependency detected: repositories.UserRepository --> @UserRepository.constructor[16] --> repositories.ConversationRepository --> @ConversationRepository.constructor[1] --> repositories.UserRepository at ResolutionSession.pushBinding (node_modules/@loopback/core/node_modules/@loopback/context/src/resolution-session.ts:228:13) at Binding.getValueOrProxy (node_modules/@loopback/core/node_modules/@loopback/context/src/binding.ts:576:13) at...

> Do you mix components from different releases? > > Also, I need to check how core versions differ. > > What is for sure, the change responsible for it...

Unless I'm missing something in the documentation, it's not possible to tell the update generator to create a set compatible with a given component, e.g. `@loopback/[email protected]`. Downgrading `@loopback/cli` before-hand also...

> Does removing the check for circular dependency helps? Commenting out the `throw new Error(msg);` in `pushBinding` indeed works just fine!

I finally found the difference between the repro-repo and our API, that made our API work with `@loopback/[email protected]`. Our `UserRepository` is a singleton! I added some commits to https://github.com/0x0aNL/loopback-next/tree/hmt-circdep-regression. The...

Questions about updating the PR: - Should I commit changes in a single commit with a message like "fix: add explanatory comments"? - Alternatively, should I squash with existing commits?...

Finally gotten around to update this PR. I did rebase and squash however, so I'll describe the changes: Next to adding several comments and renaming some variables based on the...

I've managed to get facemark.Fit to work using 4.1.0, but with some editing involved. I'm quite sure it's not the right way to do it, but at least it works....