Installing the latest version of this package results in yarn warnings about workspaces
See original GitHub issueWhat version of React, ReactDOM/React Native, Redux, and React Redux are you using?
- React: 16.14.0
- ReactDOM/React Native: 16.14.0
- Redux: 4.0.5
- React Redux: 7.2.5
What is the current behavior?
[3/4] Linking dependencies...
warning Workspaces can only be enabled in private projects.
warning Workspaces can only be enabled in private projects.
[4/4] Building fresh packages...
What is the expected behavior?
No warnings.
Which browser and OS are affected by this issue?
No response
Did this work in previous versions of React Redux?
- Yes
Issue Analytics
- State:
- Created 2 years ago
- Reactions:7
- Comments:13 (6 by maintainers)
Top Results From Across the Web
Installing the latest version of this package results in ... - GitHub
Hey team, I have noticed a warning message stemming from your dependency in our codebase. Before adding @swc/jest to our dependencies yarn ......
Read more >yarn install
json ), Yarn looks for the newest versions available that satisfy the constraints in package.json . The results are written to yarn.lock ....
Read more >yarn not installing packages from workspace but instead tries ...
I have based my project off of the npx create-turbo@latest command. I have eslint-config-custom and tsconfig projects inside my /packages folder ...
Read more >A guide through The Wild Wild West of setting up a mono repo ...
In this part, I will explain step by step how to setup Lerna, Yarn Workspaces and Typescript in a mono repo. In the...
Read more >Introducing Yarn 2 ! - DEV Community
The yarn package on npm will not change; we will distribute further version using the new yarn set version command.
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 FreeTop 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
Top GitHub Comments
Huh, that’s… weird. And annoying. (Technically the problem would be #1810 for the
v7
branch, but same difference.)Well, couple options. The “workspaces” thing was only to add the docs folder so it all gets installed at once. Easy enough to drop that.
Alternately, we could do some silly “rewrite the package file before publishing” shenanigans or something.
I just published 7.2.6, which removes the workspace and should get rid of the warning.