TypeScript Full Stack project (Part III) - NestJS, the server-side
TypeScript Full Stack

TypeScript Full Stack project (Part III) - NestJS, the server-side

Creating a NestJS application used in the server-side to show the advantages to use TypeScript for your entire project stack.

TypeScript Full Stack project (Part II) - Client-side
Creating a simple angular application used in the client-side to show the advantages to use TypeScript for your entire project stack.

The previous post showed the client-side part. Now, we are going to create the server-side using NestJS. That team has done a very great job with the framework but also has awesome documentation as well. If you still not knowing NestJS, I strongly recommend you to take a look.


Server-side

Let's go to create the NestJS application that we use it as server-side part using its CLI and the following options:

  • package-manager: npm. I prefer npm than yarn and I am using it inside the rest of the project.
odin@asgard:~/issues $ nest new server --package-manager npm

The new folder structure will contain a new folder server, with the NestJS application.

issues
  ├── client
  ├── .git
  ├── .gitignore
  ├── package.json
  └── server

To start the server from the parent folder, issues, we are going to modify the package.json adding a new start:server script.

{
  ...
  "scripts": {
    "start:server": "npm start --prefix ./server"
  },
  ...
}

Now we are able to start the NestJS application:

odin@asgard:~/issues $ npm run start:server

Because of the purpose of this post is not to build a NestJS application, you can get the server-side code from this repository.

If you want to know more about how to use the NestJS CLI, Kamil Mysliwiec has written a very interesting post.

Announcing NestJS Monorepos and new CLI commands
Learn how to manage multiple NestJS projects in a single monorepo using the NEW NestJS CLI features, and other great new tools!

In the next post, I am going to explain how to create the shared libraries part.

TypeScript Full Stack project (Part IV) - Shared Libraries
An advantage to use TypeScript for your entire stack, creating shared libraries for your client and server side.

Also, you can see all the post series here:

TypeScript Full Stack
TypeScript for all your platform building an Angular application for the client-side and using NestJS framework to build the server-side.

Share Tweet Send
0 Comments
Loading...
You've successfully subscribed to YggdrasilTS
Great! Next, complete checkout for full access to YggdrasilTS
Welcome back! You've successfully signed in
Success! Your account is fully activated, you now have access to all content.