-
-
Notifications
You must be signed in to change notification settings - Fork 196
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
On adding test frameworks their peerDependencies are not installed #2283
Comments
Problem Only occurs when the user has installed globally npm version 3.x. The difference between npm 2.x and 3.x is that, npm 2.x installs all peer-dependencies of a package and npm 3.x does not. {
"name": "some-dependency",
"version": "1.0.0",
"peer-dependencies": {
"peer-dep-1": "0.0.1"
}
} So if we do: Possible solutions
|
@Plamen5kov how about leaving the responsibility of installing dev peer dependencies to the developer? Messages output by npm are verbose enough where peer dependencies are concerned. |
related to #2212 (comment) |
I think that after seeing the message about the unmet peer dependency -its clear what you have to do. However, it would be great to update the docs with a note that you will have to manually add a dependency based on the testing framework you choose. It would help people who just follow the guide. @Pip3r4o moving |
#2693 fix |
CLI is now adding peer dependencies, but the problem is that |
I believe the To add the required depdendencies (as |
The issue is still reproducible .. running
is failing with
|
Steps to reproduce:
Expected result: Tests are executes and results are shown
Actual result: Exception
Error: Cannot find module 'jasmine-core'...
The text was updated successfully, but these errors were encountered: