Dependency issues with latest version
See original GitHub issueI’m submitting a…
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:
Current behavior
[3/4] Linking dependencies...
warning " > postcss-ng-tailwind-in-components@0.0.2" has unmet peer dependency "postcss@^8.2.4".
warning " > tailwindcss@2.0.2" has unmet peer dependency "autoprefixer@^10.0.2".
warning " > tailwindcss@2.0.2" has unmet peer dependency "postcss@^8.0.9".
warning "tailwindcss > postcss-nested@5.0.3" has unmet peer dependency "postcss@^8.1.13".
Expected behavior
No dependency warnings
Minimal reproduction of the problem with instructions
Create new Angular 11.1.1
app
Add @ngneat/tailwind
schematics
Adding the missing postcss
and autoprefixer
dependencies manually solved the problem.
What is the motivation / use case for changing the behavior?
No dependency warnings
Environment
Angular version: X.Y.Z
/ \ _ __ __ _ _ _| | __ _ _ __ / ___| | |_ _|
/ △ \ | '_ \ / _` | | | | |/ _` | '__| | | | | | |
/ ___ \| | | | (_| | |_| | | (_| | | | |___| |___ | |
/_/ \_\_| |_|\__, |\__,_|_|\__,_|_| \____|_____|___|
|___/
Angular CLI: 11.1.2
Node: 15.7.0
OS: linux x64
Angular: 11.1.1
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
Ivy Workspace: Yes
Package Version
---------------------------------------------------------
@angular-devkit/architect 0.1101.2
@angular-devkit/build-angular 0.1101.2
@angular-devkit/core 11.1.2
@angular-devkit/schematics 11.1.2
@angular/cli 11.1.2
@schematics/angular 11.1.2
@schematics/update 0.1101.2
rxjs 6.6.3
typescript 4.1.3
Browser:
- [x] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
For Tooling issues:
- Node version: v15.7.0
- Platform: Ubuntu
Issue Analytics
- State:
- Created 3 years ago
- Comments:12 (2 by maintainers)
Top Results From Across the Web
How to fix npm dependency hell - Sylhare's blog
Which version of the package has been installed? Update/Set the wanted version in your package · What are the breaking changes coming with...
Read more >NPM Dependency errors? Then You're doing it wrong. - Medium
The answer is bad dependency tree management. This is a common problem within the NPM ecosystem which every developer faces.
Read more >Dependency hell - Wikipedia
The dependency issue arises when several packages have dependencies on the same shared packages or libraries, but they depend on different and incompatible ......
Read more >How to Ensure That Your Dependencies Are Up to Date
Applications may encounter dependency issues for the following reasons: ... New versions contain new features, so you must meet hardware and ...
Read more >Troubleshooting Dependabot errors - GitHub Docs
Investigating errors with Dependabot version updates. Understanding Dependabot errors. Dependabot cannot update DEPENDENCY to a non-vulnerable version.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Same issue with a fresh
ng new some-app-name
Using
“@angular-builders/custom-webpack”: “11.0.0”
I picked
scss
and am usingyarn
in the initial setup if that makes a differenceyarn add --dev postcss@8
Fixed it for me
I hit the same situation. Today I executed the commands below and
postcss@8
is missing.It’s able to be solved by
npm install -D postcss@8
. Until that,node_modules/postcss
is still version 7.