Unable to add packages or plugins | expected workspace package to exist for X
See original GitHub issueCurrent Behavior
I try to yarn add @backstage/plugin-catalog-backend-module-ldap
and it errors because apparently I need css-loader
installed in my workspace. 🤔
Expected Behavior
The plugin just installs without error.
Steps to Reproduce
Create a new backstage app and try to yarn add @backstage/plugin-catalog-backend-module-ldap
in packages/backend
.
Context
I’m trying to import users and groups from an LDAP-compatible service. I tried step 1 of the official documentation and failed.
Your Environment
- NodeJS Version (v12): 14.16.1
- Operating System and Version (e.g. Ubuntu 14.04): macOS Big Sur
- Browser Information: N/A
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:11 (10 by maintainers)
Top Results From Across the Web
yarnpkg - Why does Yarn throw "Invariant Violation: expected ...
Run yarn to install all dependencies; Run yarn upgrade-interactive. But I get the exact same error. I went scavenging for answers and none...
Read more >Problems and Solutions - TerriaJS
Problem. When using yarn workspaces to develop a TerriaMap against a custom version of terriajs yarn install throws error. An unexpected error occurred ......
Read more >Error Codes | Yarn - Package Manager
This informational message occurs when Yarn wishes to let you know that a package will need to be built for the installation to...
Read more >Troubleshooting - Unity - Manual
Back up and then delete the package sources in your project's Packages folder, leaving only the manifest.json file. Then try to reload the...
Read more >Introducing Yarn 2 ! - DEV Community
are now aware of workspaces; Running yarn install can be made optional ... And since we now allow building Yarn plugins, you'll be...
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
This is actually something that effects all installs of things in the workspace. Been unable to work out what the issue is though. @OrkoHunter I think had a workaround, but you can add the package explicitly in the
package.json
manually and runyarn install
for nowJust following up with this, looks like upgrading to latest 1.x release of yarn doesn’t help, but updating to
berry (2.x)
seems to fix the issue too and I can install as expected. Maybe we can fix this short term for now, but look at moving to 2.x otherwise I think this is going to keep cropping up and causing issues blocking us from upgrading versions.@Rugvip I know you had some thoughts on berry or had tried it, what were your findings?