Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
d3 peer dependencies
See original GitHub issueI’m submitting a … (check one with “x”)
- bug report - search github for a similar issue or PR before submitting
- feature request
- support request - use StackOverflow (add the
ngx-chartstag) or the gitter chat for support questions
Current behavior
package.json declares each d3 package as a dependency as well as a peerDependency. Would expect peerDependency & devDependency or just dependency. This results in unnecessary warnings.
Expected behavior
Declare d3 packages as dependencies, peerDependencies seems extraneous.
Reproduction of the problem
yarn / npm install
What is the motivation / use case for changing the behavior? No need for extra packages
Please tell us about your environment:
- ngx-charts version: 10.0.0
- Angular version: 7.0.2
- Browser: all
- Language: all
Issue Analytics
- State:
- Created 5 years ago
- Reactions:13
- Comments:15 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Any reason swimlane still uses 4.x instead of 5.x?
This is the worlds easiest fix, what is the hold up here? Do I need to make a PR?