You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure about the policy in this matter, but I've found one inconsistency while trying to run the project.
When I spinned up this project on netlify from the github repo, everything works fine out of the box. It worked both for manual installation (creating repo first and then importing to netflify) and the direct start from the templates.
The problem occured when I tried to run the same project from the bitbucket repo. I couldn't find any explicit error, but the page hasn't been deployed correctly. Deploy was successful with cypress errors and page was not found when visiting the production url.
After digging up I've finally realised that when you spin up the project from github, netlify detects that this is a next.js app and applies the @netlify/plugin-nextjs plugin under the hood (it's visible in the UI plugins section). In case of bitbucket I had to do that step manually within the UI or add config section:
[[plugins]]
package = "@netlify/plugin-nextjs"
along with adding proper dev dependency to package.json.
If this plugin is required to correctly run the app in the netlify, maybe it's better to add it to the config, to avoid inconsistencies across multiple git providers? Alternatively netlify plugin that autodetects the project's framework could be improved, but IMHO explicit dependencies seems to be cleaner and allow to avoid similar issues in the future.
Thanks for the starter anyway. It's really helpful! :)
The text was updated successfully, but these errors were encountered:
This is super helpful feedback, thank you for issuing this report. What I'm gonna do is get this reproduced and also deliver this feedback to our frameworks and build system teams to see what might be the situation.
Like you said, Netlify should be auto-detecting the fact this is a Next.js project so it is interesting that for some reason the source affected this. One last question I had is, when you say you were using bit bucket which workflow were you using? Like you used the DTN button and connected it to Bitbucket there or were you going through the UI where it says "start with a template"?
Hi @maxcell! In my case I couldn't use "start from a template" flow with bitbucket, because I see only github as an available option as below 👇
I manually downloaded the project, created fresh repo on bitbucket then used "add new site" > "import an existing project", this way I had option to select more git providers than just github. Hope it helps and sorry for the delay :P
Not sure about the policy in this matter, but I've found one inconsistency while trying to run the project.
When I spinned up this project on netlify from the github repo, everything works fine out of the box. It worked both for manual installation (creating repo first and then importing to netflify) and the direct start from the templates.
The problem occured when I tried to run the same project from the bitbucket repo. I couldn't find any explicit error, but the page hasn't been deployed correctly. Deploy was successful with cypress errors and page was not found when visiting the production url.
After digging up I've finally realised that when you spin up the project from github, netlify detects that this is a next.js app and applies the @netlify/plugin-nextjs plugin under the hood (it's visible in the UI plugins section). In case of bitbucket I had to do that step manually within the UI or add config section:
along with adding proper dev dependency to package.json.
If this plugin is required to correctly run the app in the netlify, maybe it's better to add it to the config, to avoid inconsistencies across multiple git providers? Alternatively netlify plugin that autodetects the project's framework could be improved, but IMHO explicit dependencies seems to be cleaner and allow to avoid similar issues in the future.
Thanks for the starter anyway. It's really helpful! :)
The text was updated successfully, but these errors were encountered: