[ Chore ] Move server to .ts

[kewinzaq1]

No description provided.

[kewinzaq1]

Before the placement of these rules was incorrect

[dev-xo]

Hello @kewinzaq1, I appreciate the efforts and the Pull Request.

Could you explain where you got the references for the implementation, or the steps of it?

• I will review the pull request, clean it a bit, and this will probably be a merge.

Solves: #232

[kewinzaq1]

Hello @kewinzaq1, I appreciate the efforts and the Pull Request.

Could you explain where you got the references for the implementation, or the steps of it?

• I will review the pull request, clean it a bit, and this will probably be a merge.

Solves: #232

Hello @kewinzaq1, I appreciate the efforts and the Pull Request.

Could you explain where you got the references for the implementation, or the steps of it?

• I will review the pull request, clean it a bit, and this will probably be a merge.

Solves: #232

HI @dev-xo I did it based on The Epic Stack https://github.com/epicweb-dev/epic-stack

[dev-xo]

This is about to be merged @kewinzaq1.

• Do you know if any of these changes will impact deployment somehow? In case we should update something else.

[dev-xo]

Made a first deployment attempt. Although everything seems to work as expected in terms of deployment, the server is not able to initialize the app, and not sure why, as the run command has not changed.

Will give it another try later, in order to recheck this.

• Will also try to deploy the main repo without this PR's effects.

---

Moved execa to dependencies, instead of devDependencies (in a private repository), in the same way Epic Stack seems to have it configured.

• After deployment, this still doesn't seem to work either.

---

Leaving this PR open, as probably someone else will be curious about it, and we can keep discussing it, looking for a fix or for ways to handle this.

[kewinzaq1]

Made a first deployment attempt. Although everything seems to work as expected in terms of deployment, the server is not able to initialize the app, and not sure why, as the run command has not changed.

Will give it another try later, in order to recheck this.

• Will also try to deploy the main repo without this PR's effects.

Moved execa to dependencies, instead of devDependencies (in a private repository), in the same way Epic Stack seems to have it configured.

• After deployment, this still doesn't seem to work either.

Leaving this PR open, as probably someone else will be curious about it, and we can keep discussing it, looking for a fix or for ways to handle this.

Thanks for the information. I'll check this