Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Yarn warning ./node_modules/react-native-purchases/package.json having the workspaces field set #840

Closed
5 tasks done
Yonom opened this issue Jan 14, 2024 · 2 comments
Closed
5 tasks done
Labels
bug Something isn't working

Comments

@Yonom
Copy link
Contributor

Yonom commented Jan 14, 2024

Describe the bug

./node_modules/react-native-purchases/package.json has the workspaces field set.

During yarn install, I get the following warning:

warning Workspaces can only be enabled in private projects.

The warning does not call out react-native-purchases, but this warning only appears when react-native-purchases is added to the dependencies. Related yarnpkg/yarn#8580 (comment)

Repro

  1. Go in a completely empty folder outside any packages
  2. yarn add react-native-purchases
  3. Observe the logs

  1. Environment
    1. Platform:
    2. SDK version: 7.15.0
    3. OS version:
    4. Xcode/Android Studio version:
    5. React Native version:
    6. SDK installation (CocoaPods + version or manual):
    7. How widespread is the issue. Percentage of devices affected.
  2. Debug logs that reproduce the issue
  3. Steps to reproduce, with a description of expected vs. actual behavior
  4. Other information (e.g. stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc.)

Additional context

Yarn v1.22.21, Node v20.11.0, MacOS 14.2.1

@Yonom Yonom added the bug Something isn't working label Jan 14, 2024
@RCGitBot
Copy link
Contributor

👀 We've just linked this issue to our internal tracker and notified the team. Thank you for reporting, we're checking this out!

@rglanz-rc
Copy link
Contributor

Hi @Yonom,
Thanks for bringing this up! It looks like that warning is coming from a pretty old yarn issue. Unfortunately if we remove that line from the code, it breaks things.

So we are discussing internally some solutions/workarounds. But for now, it is safe to ignore that warning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants