Unfortunately we donāt provide support to private repositories.
Could you replicate your issue (only the portion of the code that provokes the issue) in a public repository (or codesandbox) so any member of the community (Frontity team included) can help you with your issue?
Could you run npx frontity info (Iād like to see if you are using any packages that might be causing this issue and what version of node youāre on)
thank you so much for coming back to me about this. I was already getting to start desperate.
Just to say a few things, also referring to @juanmaās answer.
I completely understand the situation and I donāt expect you guys to debug/fix my issue. It is however something that was suggested so I wanted to offer access to my repository.
This aside, all I wanted was to get some help with debugging this and getting to the bottom of it, as I am completely clueless how to find the issue in a situation where the error is so vague. I would love to find the solution, just some directions are needed
i tested this and the manual serve works on localhost. However I am not certain how it should work when deploying my app to my VPS? Which port do I need to use? Will that create some conflicts?
You can use any port you want, like when using npx frontity serve. Just set it on the file.
Ok, thatās good news! It means the problem is on the CLI.
Could you please create a new project, with mars-theme for example, and slowly add all your npm packages, one by one, running npx frontity build && npx frontity serve in between until you find the one that makes it fail?