Installing the latest version of this package results in yarn warnings about workspaces

[kaiyoma]

What 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

[kaiyoma]

Initially filed this against redux-devtools (reduxjs/redux-devtools#854), but the author there directed me to file the issue here.

The workspaces property can be easily found by searching through node_modules:

$ find node_modules/ -name package.json | xargs grep workspaces
node_modules/@redux-devtools/app/node_modules/react-redux/package.json:  "workspaces": [
node_modules/@redux-devtools/core/node_modules/react-redux/package.json:  "workspaces": [

[timdorr]

Looks like this is caused by #1751. I guess they expect the top level workspace not to be published. Kind of a crappy requirement, IMHO. Maybe we can stripe this during publishing somehow?

[markerikson]

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.

[obaydmir]

Any solution for this issue?

[markerikson]

@obaydmir Not exactly. We'd need to switch back to having the docs not be a "workspace", and do a new release. We're busy with a lot of other stuff atm and fixing this is not a high priority, especially given that it's just a single warning on install for a smaller portion of the userbase.

[obaydmir]

@obaydmir Not exactly. We'd need to switch back to having the docs not be a "workspace", and do a new release. We're busy with a lot of other stuff atm and fixing this is not a high priority, especially given that it's just a single warning on install for a smaller portion of the userbase.

I understand. No pressure. Not really a dealbreaker issue, just wanted to know the status. The info you have to send will place it in context and manage the expectations. We will have to wait for the perfect solution.

[rgoldfinger-quizlet]

No pressure, but I wanted to share what this looks like in our monorepo:

[timdorr]

I just published 7.2.6, which removes the workspace and should get rid of the warning.

[rgoldfinger-quizlet]

Thank you so much! Certainly wasn't expecting it to be fixed so quickly, but it's much appreciated.

[markerikson]

c'mon Tim now no one's gonna believe anything I say about scheduling or task prioritization if you keep fixing things this fast

[Gaphell]

I am seeing this in my workspace as well. Not sure if it's due to upgrading the webpack to v5.

[markerikson]

@Gaphell Per above, this should have been fixed in 7.2.6. What version do you have installed?

[Gaphell]

@Gaphell Per above, this should have been fixed in 7.2.6. What version do you have installed?

@markerikson, my bad, I was using 7.2.5. Thanks.