Skip to content

Remove unneeded peers #139

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

Merged
merged 1 commit into from
May 7, 2025
Merged

Remove unneeded peers #139

merged 1 commit into from
May 7, 2025

Conversation

NullVoxPopuli
Copy link
Contributor

embroider, auto-import, and ember-cli before them handled virtual deps without a package.json entry.

package.json entries win over virtual deps, so we don't want to declare ember-source or @glimmer/tracking as peers.

Related:

@NullVoxPopuli NullVoxPopuli added the bug Something isn't working label May 7, 2025
Copy link

vercel bot commented May 7, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
reactive ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 7, 2025 4:42am

@NullVoxPopuli NullVoxPopuli merged commit 657aa99 into main May 7, 2025
13 of 16 checks passed
@NullVoxPopuli NullVoxPopuli deleted the remove-unneeded-peers branch May 7, 2025 04:45
@github-actions github-actions bot mentioned this pull request May 7, 2025
NullVoxPopuli added a commit to emberjs/ember-qunit that referenced this pull request May 13, 2025
is extraneous, and the embroider/auto-import infra know where to get ember-source from.
It's not _wrong_ to include, but it requires folks' manage their deps correctly -- so we can be a little more forgiving to maintainers by just omitting this.


From PR descriptions elsewhere:

- ember-source: removed because the embroider / auto-import know what we intend - it's not bad to have if someone manages their dep graph correctly, which is easier with pnpm, but not everyone gets it right, and folks have a hard time tracking down errors
- @glimmer/tracking removed because it's a real package, but one we don't want to use. This comes up in embroider/vite where the presence of real packages always takes precedence over virtual packages. This is actually problematic because it can break reactivity in subtle ways, even if a dep graph is correct - allowing duplicates of dependencies, which for the glimmer internals, we don't want.
 

Related:
- cibernox/ember-power-calendar#550
- lifeart/ember-click-outside-modifier#47
- tracked-tools/ember-async-data#854
- emberjs/data#9986
- ember-animation/ember-animated#779
- tildeio/ember-element-helper#125
- CrowdStrike/ember-headless-form#574
- adopted-ember-addons/ember-sortable#620
- ember-cli/ember-app-blueprint#7
- ember-cli/ember-cli#10697
- ember-cli/ember-addon-blueprint#35
- embroider-build/addon-blueprint#339
- ember-polyfills/ember-functions-as-helper-polyfill#151
- jelhan/ember-style-modifier#312
- jmurphyau/ember-truth-helpers#211
- ember-modifier/ember-modifier#949
- tracked-tools/tracked-toolbox#211
- emberjs/ember-test-helpers#1543
- NullVoxPopuli/ember-resources#1189
- NullVoxPopuli/ember-modify-based-class-resource#20
- universal-ember/kolay#187
- universal-ember/reactiveweb#139
- universal-ember/ember-primitives#471
- universal-ember/docs-support#77
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant