The following diagram illustrates the source code files generated from the last section:
![](https://static.packt-cdn.com/products/9781789341171/graphics/assets/6151ed7b-f4e8-4af0-86d6-84014bbdca75.png)
The Package.swift is used in the same way as that in a Vapor project. Your application's name, required package dependencies, and different build targets are configured in this manifest file.
A typical Kitura project is partitioned in a similar fashion as in a Vapor project; an application executable module, a test-executable module, and a core application module with all of your application logics:
- There is only one Swift file in the helloWorld executable module. It serves as an entry point for your project and does several things: It configures Kitura's Helium logger to be used in this project, creates an App() instance, and calls the instance's run() function. The entry point is implemented in a do-try-catch block to catch any...