Skip to content

Yarn Support #45

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.

Sign up for GitHub

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

Jump to bottom
Closed
vacom opened this issue Sep 27, 2024 · 5 comments · Fixed by #49
Closed

Yarn Support #45

vacom opened this issue Sep 27, 2024 · 5 comments · Fixed by #49

Comments

@vacom
Copy link

vacom commented Sep 27, 2024 •
edited
Loading

Hey, I'm trying to install this package (following the Getting Started guide from https://opennext.js.org/cloudflare/get-started) on an existing project that uses Yarn v1.22.18. However, the build fails because it seems to require PNPM. Is this an intentional design choice, or will the package support other package managers like Yarn?

This also happens with NPM if npm is set on the packageManager on package.json

UsageError: This project is configured to use yarn because package.json has a "packageManager" field
    at Engine.findProjectSpec (.....)

Node.js v22.6.0
node:internal/errors:983
  const err = new Error(message);
              ^

Error: Command failed: pnpm next build```
@cmackenzie1
Copy link

Facing this issue as well but trying to use just npm instead of pnpm

@dario-piotrowicz dario-piotrowicz mentioned this issue Sep 30, 2024
Merged
@dario-piotrowicz
Copy link
Contributor

Hi @vacom, thanks for the issue 🙂

The fact that pnpm is being used to build the application is something we put in just for the same of quickly implementing the prototype it's not a intentional design choice/restriction.

I've opened #49 which should hopefully address this, both for yarn and npm (and bun)

@dario-piotrowicz
Copy link
Contributor

@vacom PR merged please try again with the latest release and let me know how it goes 🙂🙏

(@cmackenzie1 as well 🙏)

@vacom
Copy link
Author

vacom commented Sep 30, 2024

It's no longer complaining because of yarn, it's entering in the build process, only now it's getting the same error that someone opened here #42

Thanks for the fix!

@vacom vacom mentioned this issue Sep 30, 2024
Closed
@dario-piotrowicz
Copy link
Contributor

@vacom thanks for confirming that it works now 😄

I'll be looking into #42 tomorrow 👍

@vacom vacom mentioned this issue Oct 3, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

run the next build command using the correct package manager opennextjs/opennextjs-cloudflare
3 participants
@vacom @cmackenzie1 @dario-piotrowicz