Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@glimmer/component is in both deps and peers #20689

Merged
merged 1 commit into from May 3, 2024
Merged

@glimmer/component is in both deps and peers #20689

merged 1 commit into from May 3, 2024

Conversation

ef4
Copy link
Contributor

@ef4 ef4 commented May 2, 2024

It doesn't really make sense to have the same dependency in both peerDependencies and dependencies. I think this was introduced as a mistake when the various @glimmer packages were moved to dependencies for typescript support.

This PR keeps the peerDependency, removes the dependency, and introduces a devDependency so we can satisfy our own peer requirement in development.

It doesn't really make sense to have the same dependency in both peerDependencies and dependencies. I think this was introduced as a mistake when the various `@glimmer` packages were moved to dependencies for typescript support.

This PR keeps the peerDependency, removes the dependency, and introduces a devDependency so we can satisfy our own peer requirement in development.
@ef4 ef4 added the Bug label May 2, 2024
@ef4 ef4 merged commit 222aebd into main May 3, 2024
26 checks passed
@ef4 ef4 deleted the fix-glimmer-peer branch May 3, 2024 12:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants