Philippe Serhal
Philippe Serhal
Closing as stale. Please feel free to reopen if this is still an issue with the v5 release. Thanks!
@orinokai make sure to change from `feat:` to `chore:` or `ci:` if we merge this. We don't need a release or release notes for this one.
@HubertHalim Can you confirm whether this is still occurring with v5 of the runtime and Next.js 13.5+? Otherwise, we'll close this issue since it's been over a year.
I'm closing this since there hasn't been any activity in over a year. Feel free to start a new thread on https://answers.netlify.com/ if you need more support.
Thanks so much for the investigation and the fix @Florian-Mt! It looks like this may have regressed when that detection was introduced to the `deploy` command in https://github.com/netlify/cli/commit/111967cc13f8524eb7e3726e1815801ccc5e0133 (v17.33.4, although...
This should be fixed in v20.0.4. Can anyone here confirm? `npm i -g netlify-cli@latest` Thanks!
@mklueh > @serhalp @Florian-Mt but can this be considered a real fix for the original problem, or rather a fix to make the hackaround work? > > I feel like...
@goastler > I wasted half a day trying to overcome this issue. Issue is present in v20.1.1 but not in v20.1.0 Are you referring to the original issue in this...
@goastler can you please run this (from the same directory) and share the output? ```sh npx @netlify/build-info ```
@eduardoboucas is this still something you'd like to get shipped?