Using <LinkTo> dynamic @route inside engines does not work as expected

I’ve an Ember app (3.16) containing an in-repo addon “ui” and an in-repo engine “admin”. Both the app and the engine share this addon. One of the components of the addon contains a dynamic <LinkTo> usage like below:

{{#each @menuItems as |menuItem|}}
  <div class="main-navbar-item">
    {{#if menuItem.model}}
      <LinkTo @route={{menuItem.route}} @model={{menuItem.model}}>
        {{t menuItem.textKey}}
      </LinkTo>
    {{else}}
      {{!-- Tried this approach as well
      {{#link-to menuItem.route}}
        {{t menuItem.textKey}}
      {{/link-to}} --}}
      <LinkTo @route={{menuItem.route}}>
        {{t menuItem.textKey}}
      </LinkTo>
    {{/if}}
  </div>
{{/each}}

Using this component inside the host app renders the links well and as expected. While trying to use the same component in the engine and rendering the same, throws the following error:

Error: Assertion Failed: You attempted to update `route` on `(unknown object)`, but it had already been used previously in the same computation.  Attempting to update a value after using it in a computation can cause logical errors, infinite revalidation bugs, and performance issues, and is not supported.

`route` was first used:

- While rendering:
  ----------------
    unknownObject.route
...

Am I missing something or is this a bug?

[abhilashlr]

@buschtoens @villander can you please take a look at this issue and the PR made?

[chancancode]

I submitted a PR to ember to fix this, can I get a review from people who are more familiar with engines?