TypeScript and NodeJS: The Proper Setup!

Let's set up TypeScript with NodeJS properly! To do that, we'll take a look at what precompiling is, to then look at how TypeScript gets compiled to Javascript in action. Really interesting stuff. And after understanding that, we can take a look at an npm-package that does that stuff under the hood for us.
Thanks for watching, I hope you found this as interesting as I did! Cheers

[@piiaall]

Your explanation is very clear

[@kurtking4662]

Enjoyed watching your video!

[@phongnguyen.5322]

Many help, thank you

[@greggsworld4453]

This was great! Thank you so much. It would be great if you added server restart on code changes to avoid having to start and stop - like nodemon.

[@Theforrestfire217]

Hi greggsworld. You should be able to do that with something like this:
"dev": "tsc-watch --onSuccess \"yarn start\"",
"start": "node dist/app.js"
using tsc-watch will keep an eye out for code changes

[@user-qn8if8bb7x]

Amazing!

[@reihane2325]

thanks , so helpful

[@NoName-qu3tw]

Great! Thank you!

[@LorenzoJimenez]

You actually forgot to install typescript as a full complete explanation. Thanks for the video

[@piotrjasiulewicz408]

god tier level video

[@joachimpenserot8651]

Hey, can you make a video explaining hot set up next-auth with a local database?

[@ballonura]

Why dir called "server" and no "src"? (naming best practice)

[@kevinolds9614]

I was going to ask this. Still, great video.

[@ilearncode7365]

how does tsc still work after you moved it into a folder? That doesnt make sense.

[@onequy6648]

gooodddd, thank youuuu

[@muhammadbilalmalik7292]

how tsc command is automatically executing server/index.ts ?

[@okage_]

do you have a link to your github or is it private

[@scorcism.]

subscribed

[@ponchobob]

maybe for some others here a simple or stupid question, but is nodejs used in big companies for their backend? or is this just some sort of "hobby backend library" ?

[@0xSLN]

Probably the biggest in the industry. What else compares in adoption?
Low level systems use a lot of C but companies want many good devs and good libs. So community size is a proxy for that. Js has biggest community, node is server js.

[@tropicalreptile6288]

yeah LinkedIn and nasa are just hobby backend thing

[@redeemr]

@@0xSLN javascript is so big because it is basically required on the front-end. On the back-end, there are tons of options that are faster and more mature than node.js. I doubt it's the most popular.

[@0xSLN]

@@redeemr Its based on number of projects on github. But popular doesn't equal best, lots of langs that are better at specific things.

[@samking618]

Express has around 22M+ weekly downloads as of today

[@ramiworkstation]

Sweet like Sugar 🍬🍬

[@mikeonthebox]

8:20 Wait what? That wouldn't work on Browsers, you can't import a Node Library like the fs one, in a browser, right?

[@redeemr]

node doesn't run in browsers.

[@amvids9348]

had the same doubt, yeah ur correct, brainfade from the guy.

[@naumanshigri]

belot han ongs na sokor yaa

[@WarframeCrunch]

I don't know why I'm getting this error :/
\middleware\errorHandler.ts:45
export default errorHandler;
^^^^^^
SyntaxError: Unexpected token 'export'
My server.ts file:
const express = require("express");
const errorHandler = require("./../middleware/errorHandler");
const dotenv = require("dotenv").config();
const app = express();
const port = process.env.PORT || 5000;
app.use(express.json());
app.use("/api/contacts", require("./../routes/contactRoutes"));
app.use(errorHandler);
app.listen(port, () => {
console.log(`Server running on port ${port}`);
})
and
errorHandler.ts file:
import {Request, Response} from 'express';
type typeErrorHandler = {
err: {message: string, stack: string[]},
req: Request,
res: Response,
next: string,
}
const errorHandler = ({err,req,res,next} : typeErrorHandler) =>{
const statusCode = res.statusCode ? res.statusCode : 500;
switch (statusCode) {
case 400: res.json({
title: "Validation Failed",
message: err.message,
stack: err.stack,
})
break;
case 401: res.json({
title: "Un authorized",
message: err.message,
stack: err.stack,
})
break;
case 403: res.json({
title: "Forbidden",
message: err.message,
stack: err.stack,
})
break;
case 404: res.json({
title: "Not found",
message: err.message,
stack: err.stack,
})
break;
case 500: res.json({
title: "Server Error",
message: err.message,
stack: err.stack,
})
break;
default:
console.log('No error, all good.');
break;
}
}
export default errorHandler;

[@redeemr]

you're mixing require and esm syntax. You should look into what adding "type": "module" does or what using the .cjs and .mjs file extensions do. I'm sure you've already solved the problem but I'm just leaving this here for future reference.