-
Notifications
You must be signed in to change notification settings - Fork 139
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
support detect and use corresponding manager and fix windows related error #34
Conversation
Seems like support for Route Group cant be achieved by simply add experimentalResponseStreaming detection, so i removed it |
This PR solved my exact issue. For reference, I got the following error:
|
|
Is this ready to merge? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would recommend you revert the formatting changes. Cloudflare uses tabs in most of its JS/TS projects these days since they're better for accessibility. See cloudflare/workers-sdk#1298 for details.
Adding an .editorconfig
and prettier config is a good idea - but I'd grab it from https://github.com/cloudflare/wrangler2 and in another PR.
I have changed the formatting config, same as the config of wrangler2 |
@LOLBRUHNICE how is this different than the PR I opened? |
First, I noticed that your pr only utilize the package manager when installing vercel, for the building it still use npx, so I created this pr to fully utilize the consumer package manager. Instead of installing vercel, I made it directly use dlx for yarn and pnpm, and use npx for npm(though yarn classic still need to install the vercel first) Than I noticed that there are also some windows related issue so I also changed some code to solve those problems |
so there are differences between your pr and this pr |
Would love this to be merged, so I could finally use next-on-pages after a month of waiting #52 |
Please merge 🙏🏻 |
Hello @LOLBRUHNICE Thank you so very much for this PR, and sorry it hasn't been reviewed in a while 🙇 I am sorry for being a bother but this PR is quite large and broad in scope so it's quite difficult to tackle, moreover it contains some code that goes against changes we applied recently, like the use of package managers: #71 (or the Windows fix that is being addressed by #86) (I also did open a PR with prettier since by its title and description I didn't think this PR was setting it up: #90) If it were not too much trouble it would be fantastic if you could remove everything from this PR that isn't specific for point Again I am very sorry for this, we've had issues with finding the time to address PRs and some like this haven't gotten the attention they deserved, we're putting a significant effort to improve this and try to reviews PRs from now on much more swiftly. Also we hope you will continue contributing to the project, if you do, please try to keep PRs smaller and more focused so that they are easier and quicker to review and merge (and other PRs implementing the same changes don't go against it) |
ok, I will create a new pr and try to keep the changes as simple as I can |
@LOLBRUHNICE thank you so very much! sorry about it again 🙇 |
This PR is created to achieve the following things:
spawn npm ENOENT
error occured when running on windowsFixes #52