Not compatible with "@glimmer/component": "^2.0.0"

[johanrd]

Build an app with embroider, this addon + "@glimmer/component": "^2.0.0". See error:

Some V1 ember addons are resolving as incorrect peer dependencies. This makes it impossible for us to safely convert them to v2 format.

app@0.0.0 -> ember-mobile-menu@5.1.0 -> ember-modify-based-class-resource@1.1.1
app@0.0.0 -> ember-mobile-menu@5.1.0 -> ember-modify-based-class-resource@1.1.1
    sees peerDep @glimmer/component@1.1.2
      at app/node_modules/.pnpm/@glimmer+component@1.1.2_@babel+core@7.26.0/node_modules/@glimmer/component
    but app@0.0.0 is using @glimmer/component@2.0.0
      at app/node_modules/.pnpm/@glimmer+component@2.0.0/node_modules/@glimmer/component

app@0.0.0 -> ember-mobile-menu@5.1.0 -> ember-resources@7.0.3
    sees peerDep @glimmer/component@1.1.2
      at app/node_modules/.pnpm/@glimmer+component@1.1.2_@babel+core@7.26.0/node_modules/@glimmer/component
    but app@0.0.0 is using @glimmer/component@2.0.0
      at app/node_modules/.pnpm/@glimmer+component@2.0.0/node_modules/@glimmer/component

  👇 👇 👇
👉 See https://github.com/embroider-build/embroider/blob/main/docs/peer-dependency-resolution-issues.md for an explanation of the problem and suggestions for fixing it.
  👆 👆 👆

Not sure why this is happening, honestly, as both ember-modify-based-class-resource@1.1.1 and ember-resources@7.0.3 have @glimmer/component@2.0.0 in their peer deps.

See johanrd@0fc93b9 for possible fix

[nickschot]

I'll have to check if we can move @glimmer/component to peerDeps. I think there were issues with old-style apps with that but not sure anymore. Otherwise it would probably also be fixed by widening the range?