-
-
Notifications
You must be signed in to change notification settings - Fork 258
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
@ember/test-helpers v4 suggests itself to be in dependencies even when only used for test-support files #1490
Comments
Looks like you solved it? https://github.com/elwayman02/ember-scroll-modifiers/pull/1106/files in a v1 addon you need both peer and devDep |
@NullVoxPopuli I updated the issue a bit ago to be more clear what the problem is - peerDep is working but the error message does not correctly suggest that as a solution, even though it has enough information to do so. |
gotchya -- for an issue with the error message, I think you'd want to open an issue on auto-import or embroider |
Just had some successful upgrades here:
I'm going to close issue, because it seems like the issue you're encountering is elsewhere. Please let me know if you want help debugging or anything. |
As of the v4 release, this package now throws an error if used in the
addon-test-support/
directory as a devDependency:The correct pattern here is to add
@ember/test-helpers
topeerDependencies
for the package that utilizes it inaddon-test-support/
, because we do not want to cause@ember/test-helpers
to be included in production bundles for consuming applications, but we do want to ensure that@ember/test-helpers
is properly installed as a devDependency for any consumers of the package providing the test-support util, since the util imports@ember/test-helpers
and will fail if the consumer doesn't have it installed.The error message itself is incorrect:
addon-test-support
is, by definition, not "addon code", but rather code for supporting tests only. This will confuse developers who will try to move it to dependencies and erroneously add it to production builds for their consumers. The error message should be updated to be more correct and suggest adding it to peerDependencies, since we know where it's being used is not actually addon code but is(maybe) going to be used by consumers.The text was updated successfully, but these errors were encountered: