Learn how to setup Node.js with TypeScript while supporting native ES modules. Use the new NodeNext option to easily interop between CommonJS and ES modules in the same project. Full Lesson and Source Code fireship.io/le...
Пікірлер: 459
@chenlim2165 Жыл бұрын
Thanks for this! Setting up a new Node project in 2023 is: 1 hour setting up the build environment 1 hour setting up linting 1 hour getting webpack to work 1 more hour optimizing everything 3 hours researching Deno / Bun / Vite, then deciding it's not worth it 1 hour wondering if you're better off with plain JS 1 hour remembering what you wanted to build
@mucookul Жыл бұрын
That’s exactly why I skip half of that stuff
@edoardoschnell Жыл бұрын
How is vite not worth it? 90% of use cases is just install boom works
@-rate6326 Жыл бұрын
Ask c++ Devs
@kollpotato Жыл бұрын
Just do bun init
@JC-fd8ho10 ай бұрын
about what ?@@-rate6326
@iatheman Жыл бұрын
This guy is always reminding me why I 1. Hate the JS ecosystem with a passion 2. Admire the JS developers that maintain their sanity and build stuff with it
@Caborrrl Жыл бұрын
Requiring the .js extension from TS was the most stupid TS idea in long time.
@thekwoka4707 Жыл бұрын
@@Caborrrl well, it's technically the spec. The TS system is very "what the spec is". Having unsuffixed imports is not valid js.
@filipmajetic1174 Жыл бұрын
@@Caborrrl there's a compiler option "esModuleInterop" that fixes it
@Caborrrl Жыл бұрын
@@filipmajetic1174 No. The esModulelnterop is not for that or anything related to that. Wtf?
@iatheman Жыл бұрын
@@shapelessed Just realized my handle is the weird generated one. But I've been there with another stack, same pain.
@ivanb493 Жыл бұрын
I feel like it might be a good idea to cover the ts-node package next time which is nice during development
@lsudo Жыл бұрын
@@vaaski that's basically react my friend
@CTSSTC Жыл бұрын
@@vaaski tsx is for react components; we don't need that additional weight here if you're just trying to write some non-frontend code.
@CTSSTC Жыл бұрын
@@alanbixby I tend to lean into ts-node, but now it's sounding like a nightmare yet again lol; I'll have to look into esbuild kit I guess lol; yet another tool :RIP: They used to say to never use ts-node for production, then you could; all the answers are an answer in one point in time and then never again down the road as they become the "wrong answer" lol I'm just glad to have node 18 here and the older versions dying off 🎉 It's all still a pain though.
@That_Darned_S Жыл бұрын
@@lsudo No, we're not talking about react or jsx/tsx. Tsx is an npm package, does the same thing as ts-node but it's newer.
@danielegvi Жыл бұрын
@@lsudo tsx is a CLI program, short for typescript execute. it uses esbuild to transpile all imports to js in memory on demand really fast. it also supports jsx/tsx the language extension, which is a bit confusing at first.
@ukaszzbrozek6470 Жыл бұрын
Why we need to target .js files when they extensions are .ts ? It is so confusing.
@stxnw Жыл бұрын
You don't. Jeff just doesn't know about the esModuleInterop option on TypeScript.
@18.j Жыл бұрын
When you compile you run the .js file and you target the other .js files, typescript won't change your import to ts so you declare it with .js that's why...
@stxnw Жыл бұрын
@@18.j Wrong
@cyrus01337 Жыл бұрын
@@stxnw How does TS handle this then?
@paoloose Жыл бұрын
@@stxnw when I dont specify the files extension, "esModuleInterop" set to true gives me: Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext' When using .ts files, The vscode hints say: "An import path can only end with a '.ts' extension when 'allowImportingTsExtensions' is enabled.ts(5097)" When I enable it, all errors are gone, but the typescript compiler throws: "error TS5023: Unknown compiler option 'allowImportingTsExtensions'." So weird.
@CTSSTC Жыл бұрын
Every year for advent of code, I spend a majority of my time configuring my baseline JS/TS environment rather than working on the coding problems, which is fun because I get to see how much things have changed just like this video hits on 😆 Edit: I'm excited to see this full course and how it evolves ;D 🎉
@zettca Жыл бұрын
Change to Deno. You'll get TS, top-level async, ESM, external modules, linting/formatting with 0 config
@codeman99-dev Жыл бұрын
@@zettca No. I can't use Deno at work. I wouldn't learn Zig right now for the same reason. Not worth it. I need to know the node ecosystem.
@zettca Жыл бұрын
@@codeman99-dev we're talking about AoC, not work.
@codeman99-dev Жыл бұрын
@@zettca Yes. It is a great opportunity to catch up and learn what is new. It is hard to do that if you jump ship.
@marvinxu295010 ай бұрын
@@zettca Just curious, what is AoC?
@itsinphy4 күн бұрын
Thanks a lot! ❤ I was able to figure this out the hard way, but I'm glad I stumbled upon this video for a) confirming that I did it correctly and b) future references. Cheers!
@schmidtdisturbr Жыл бұрын
A thousand thank-yous for this! I wish this video were linked in the TypeScript official getting started docs. As an infrequent JavaScript developer starting to dig into the TypeScript ecosystem, the legacy module situation is a huge stumbling block to get past. Love your straightforward presentation.
@dubble_cuppachino Жыл бұрын
The module field is pretty much abandoned. It's only really used by bundlers. The correct way to tell node how to import your code is to use the "files" and “exports” fields. Not trying to sound like a stackoverflow comment, just wanted to share a thing I picked up after diving into all this stuff recently. Excited to watch the rest, I love your content!
@bellabianchi7667 Жыл бұрын
OMG I literally sat there with this exact issue an hour ago and couldn’t resolve it and this appears in my subscriptions - THANK YOU!!
@fizzdev Жыл бұрын
top notch video, can't wait for the 2024 guide
@nithinrajendran30914 ай бұрын
Did the 2024 guide drop yet? bro left us hanging..
@fizzdev4 ай бұрын
@@nithinrajendran3091 sadly not.. we'll have to wait a few more months
@TheBeastDispenser Жыл бұрын
Thank you! This could not come at a better time. For the life of me I could not get TypeScript working with my GraphQL setup but your review of the tsconfig files cleared up my confusion. My main issue was needing to add the .js file extensions to the imports.
@erwin.agpasa9 ай бұрын
me tooooo
@Grim_Nerd Жыл бұрын
I always find myself having a mini heart attack when watching your videos because you'll occasionally hear a baby crying in the background and I ALWAYS think it's my baby. I'm literally home alone right now and still paused the video to listen out for him crying :')
@shobhitsingh62715 ай бұрын
Million likes for this video! I spent the entire day debugging until I stumbled upon your video. Turns out, the issue was that I was importing a common JS package without specifying {"type":"module"} in the package.json. Thank you so much! ❤❤❤❤❤
@MisterNorthernCanuck Жыл бұрын
I spent 3 hours on fixing this. Thank you so much.
@rign_ Жыл бұрын
I need to work with pure javascript to get CommonJS working, because of dynamically use the code and re-import it on runtime is such a blessing as well a curse. But for my project and personal works, it's perfectly fine.
@LarsRyeJeppesen Жыл бұрын
That sounds horrific
@zyrenth Жыл бұрын
Amazing tutorial, It's definitely a good tutorial for beginners, keep up the good work!
@ThePotatoChronicler Жыл бұрын
Deno NPM compatibility is nearly there! We're so close. Most libraries just work OOTB already. I am running from node with the speed of light my man, at least for my personal projects
@gustavohenriquejunkes32763 күн бұрын
Just soooo coool. Great video man
@Novacification4 ай бұрын
An hour looking for a minimal typescript setup with clear explanations. I should have known to come here immediately.
@codewithguillaume Жыл бұрын
Yess!!!! I was hoping to see this video one day on your channel :)
@riddixdan5572 Жыл бұрын
I'm still confused as to why we need to specify file extention when we import. Couldn't node/TS resolve it itself based on the actual file it is importing?
@mcvgs1780 Жыл бұрын
I kind of remember Ryan Dahl spoke about this being needlessly complex to implement and (not so sure if I remember this right) hogs resources. If he were given a chance to do Node all over again he would not do it.
@dusliangames Жыл бұрын
I just use tsc-alias to fix the import file extension after compiling. It's easier and cleaner. And handles the path aliasing. I would recommend using nodenext for moduleresolution, but for the module option to use esnext or commonjs
@danish73353 ай бұрын
you don't know how much you helped me.. thanks mate
@NoPudieronConGuevara Жыл бұрын
It's truly a peculiar experience see how this channel's owner is gradually descending into madness by the hand of web technologies mostly. I just can't look away... keep the hard work
@Zagoorland Жыл бұрын
You should make a movie about package managers, only few people know about PNPM for example, but for now it's the fastest and most space efficient solution!
@LarsRyeJeppesen Жыл бұрын
And messy. The amount of time I have spent resolving fcked up symlinks is countless
@zvrk Жыл бұрын
For those that want nodemon to watch over file changes: add "ts-node": { "esm": true } to tsconfig.json And if your shell complains like mine did use ( npx nodemon src/index.ts ) this should work Also add ts-node globally with ( npm i -g ts-node ) really not sure if this is needed but I did it anyway
@ytPEDROjoao Жыл бұрын
You saved me, thank you!
@LarsRyeJeppesen Жыл бұрын
OR us tsup --watch
@ggorg0 Жыл бұрын
You forgot about strict mode in tsconfig.json!
@mmvarma.p Жыл бұрын
Great video as always. From 3.09 secs to 3.28 secs, your voice sounded different. Is it me or has anyone noticed it? R u well bro. Please stay safe and sound. Looking forward to your next video.
@beyondfireship Жыл бұрын
I have a cold. Nothing serious
@akshattamrakar9071 Жыл бұрын
I was thinking the same
@usd00 Жыл бұрын
Is it only me who feels like Jeff's voice is changing constantly over the video...?
@alecdorasandler66905 ай бұрын
Thanks a shit ton for this! I wasted so much time fixing the imports with .ts ext.
@michaelmenard8614 Жыл бұрын
Awesome video! Any chance there is a pt. 2 coming with jest, eslint, prettier, and husky?
@tacticalassaultanteater9678 Жыл бұрын
It's important to highlight that this is only one way to set up Typescript with Node in 2023. I have different priorities, revolving more around minimizing surprises than around efficiency, so I do almost everything differently, and I don't expect my values to turn around completely next year either. This tutorial is valuable because it's a complete description of an error-free setup, not because the statements within are universally optimal.
@DemPilafian Жыл бұрын
It feels like this message is trying to tell us something without actually saying what it is. Or maybe I'm just missing something obvious. Can someone express the "different priorities" in more blunt terms?
@asiraky Жыл бұрын
Or just use ts-node
@Ma1ne2 Жыл бұрын
Looking forward to part two if this video in a month when all of this changed again :D
@VideoBunt Жыл бұрын
1) ts-node + nodemon could be very helpful 2) npm i tsconfig@ for certain node version could be helpful, just extends it
@stxnw Жыл бұрын
no. ts-node is trash
@VideoBunt Жыл бұрын
@@stxnw why? And what can replace it?
@stxnw Жыл бұрын
@@VideoBunt swc-node
@LarsRyeJeppesen Жыл бұрын
ts-node is horrible. Do not use it please
@LarsRyeJeppesen Жыл бұрын
@@VideoBunt tsup (esbuild) in watch mode
@dusliangames Жыл бұрын
Importing a js file in typescript that doesn't exist on the file system is really confusing and simply weird. It's way better to use a tool like tsc-alias to fix the imports as a compilation step instead of having to change every import of every source file in every project.
@vikingthedude Жыл бұрын
Yeah I don’t like it
@adam-user Жыл бұрын
Is there a way to resolve this that works both during compile time and in VSCode?
@Zwiebelgian Жыл бұрын
Deno now supports npm (atleast that is what their propaganda says) so now may be a good time to switch
@brucewayne2480 Жыл бұрын
Why ? I just want to know what will you gain ?
@Zwiebelgian Жыл бұрын
@@brucewayne2480 Built-in Typescript support, better speed, cleaner directories. I don‘t actually know, I am not a backend developer
@brucewayne2480 Жыл бұрын
@@Zwiebelgian it's not a lot of work to setup a typescript project , cleaner directories I'm not seeing any problem, speed not sure , I've not seen any benchmarking
@jakob7116 Жыл бұрын
@@Zwiebelgian yeah, it also has better apis under the Deno. namespace and a std library. You also get less config files, lots of built in stuff like linter so you don’t have to do that yourself, more secure, faster http server, better browser compatibility, the apis mostly use promises (and sync versions) instead of callbacks, you can run code directly from a url, even Ts code and so on The npm support doesn’t work on all packages perfectly just yet but soon:tm:
@Dominik-K Жыл бұрын
For me personally the sandboxing capabilities are nice
@AnweshAdhikari Жыл бұрын
Time travel is real! Jeff is one month ahead of us!😂❤
@0brine Жыл бұрын
Lol i needed that exactly 2 days ago xD
@joseph0x45 Жыл бұрын
The video I never knew I needed, thanks Jeff :)
@SamyarBorder Жыл бұрын
evey once in a while i come back and watch this video
@user-sq6us6jl5h Жыл бұрын
Exactly what I needed . Perfect video!
@kklowd Жыл бұрын
Bruh how did you know I was setting up a project to with both esm and cjs you really are a wizard 👀
@thepowerhat Жыл бұрын
For developing nodejs backend, I generally use babel with watch mode and nodemon to have very fast server restart on file save. I'll check this out but I'll probably still prefer sticking with a faster transpiler than tsc
@double-agent-ly Жыл бұрын
why use babel when u have vite or even the newer tool, rome
@thepowerhat Жыл бұрын
@@double-agent-ly Vite for backend? Hmm
@fred.flintstone4099 Жыл бұрын
For developing frontend I use Vite for very fast hot reload on file save.
@shubitoxX Жыл бұрын
Babel is not fast
@thepowerhat Жыл бұрын
@@shubitoxXSure faster than tsc, because it just ignores the types, it doesn't type validate the AST like tsc does..
@abhaynath5833 Жыл бұрын
Madness....... ? THIS IS JavaScript ecosystem 🔥🔥🔥🔥🔥🔥
@phaZZi6461 Жыл бұрын
i was here for the module thing, thanks
@xDemorn Жыл бұрын
Can you make a tutorial on how to host a node app on IIS?
@kalebercanbrack8857 Жыл бұрын
Just yesterday I was dealing with something similar with Fastify and Typescript. I wanted to be using ESM, and went through the whole troubleshooting process to figure out the right tsconfig settings, but due to the way a lot of Fastify packages were exporting their types it broke being able to import the default export from it. I don't know the specifics, but it was just super annoying that this glorified linter was causing such an obnoxious bug for code that worked fine without it. However, Typescript in Deno is a beautiful experience. Largely I think because you don't have to worry about commonJS. Makes me wonder if as Deno gets more popular, the TS Node people will move over to it
@vaultofmyths9 ай бұрын
Except deno breaks your code in ways you can't imagine because of their weird engine
@d-landjs Жыл бұрын
Excellent tutorial!
@flatmapper Жыл бұрын
Love it! Looking forward to watching your full course. But please do it for experienced developers too
@HackSoft Жыл бұрын
Kudos for the concise & resourceful video 🙌
@srinivasnahak347311 ай бұрын
You're a magician for sure!!
@LarsRyeJeppesen Жыл бұрын
tsc? What about Turbo, EsBuild etc? Why use npm when we have pnpm?
@himanshukapoor55864 ай бұрын
"noEmit": true, "allowImportingTsExtensions": true, adding these two will allow you to import ts files as .ts files only.
@Alex-lt4kr9 ай бұрын
Thank you, i was struggling with the tsconfig trying to get the top level await feature working
@danieldosen5260 Жыл бұрын
Great use of
@salsichalivre5401 Жыл бұрын
Great, I only needed 3 minutes to give up on frontend dev.
@xrr-1 Жыл бұрын
0:45 javascript at its peak
@steveanthonyluzquinosagama7450 Жыл бұрын
That's exactly why I created typescript-project-generator. It will handle all the configs for using TS with Node.js. Give it a try :)
@NareshKumar-vt4shАй бұрын
Thanks a lot.
@stefankracht Жыл бұрын
Good timing on that video, since advent of code is around the corner ❤
@shaded443810 ай бұрын
the moth really cheered me up i cant lie
@davidnagli Жыл бұрын
Funny how this video is only a day old and I already out of date with the new Node 19 release (which supports imports without the .js file extension)
@aunimhassan7465 Жыл бұрын
life saver video
@GuildOfCalamity8 ай бұрын
Great video. This reminded me of the reason I don't like web dev... too many moving parts just to get a simple webpage to run.
@voychoi9923 Жыл бұрын
Great content as always
@resourcelookup8678 Жыл бұрын
Super
@joseandkris Жыл бұрын
This is amazing. Thank you :)
@ertagon Жыл бұрын
Do Babel next.
@twentyeightO1 Жыл бұрын
The ritual of harakiri is easier than this.
@himawaridev22 күн бұрын
use full bro
@Mauro-K Жыл бұрын
I like the video, I hated the topic, but it was good content
@kishiue Жыл бұрын
I'd advise using a runner like TSX or Esbuild runner. This strips the types and makes it much less painful to develop. Type checking is gradually moving in the direction of being a CI step rather than part of the build step.
@LarsRyeJeppesen Жыл бұрын
Agree, TSX or Esbuild - or Turbo
@Steve-Richter Жыл бұрын
was hoping you would cover how to run the equivalent of nodemon when a change is made to the typescript source code.
@user-fc3us4vb3k Жыл бұрын
Thank you so much!
@nicholaskoffler294 Жыл бұрын
looking forward to that typescript course
@SirBalls Жыл бұрын
As someone in 2023, I can confirm this is how you setup Node.js with TypeScript
@SirBalls Жыл бұрын
@@minorikoaki No, other way around
@LarsRyeJeppesen Жыл бұрын
No no no, don't use tsc, and don't use ts-node.
@SirBalls Жыл бұрын
@@LarsRyeJeppesen Sorry, in 2023, we still use tsc for some reason... I don't make the rules
@abdulazeem1880 Жыл бұрын
Please make a video on pr-commit hooks
@ricardorien Жыл бұрын
Express + TypeScript, please. With nice paths like "import ASDF from @componets/navbar" Please!
@AngelHdzMultimedia Жыл бұрын
Just add the path alias in tsconfig.json for the "@components" or even better, just point "@" to the src folder, so you can "@/anything". Then, install @types/node and @types/express as development dependencies. If you use dotenv and cors, install @types/dotend and @types/cors.
@LarsRyeJeppesen Жыл бұрын
@@AngelHdzMultimedia That won't work well in many environments.
@AngelHdzMultimedia Жыл бұрын
@@LarsRyeJeppesen yeah, there are a lot of issues in Node and TypeScript, and each bundler have its own solutions. But for now, that's the solution and packages like module-alias or better-module-alias. But if you know of a better solution, please comment it instead of being secretive about it. Cheers!
Жыл бұрын
Don't forget to add the "--enable-source-maps" flag when running your compiled code with node, otherwise the sourcemaps will be ignored.
@user-ck6yl6qb2g Жыл бұрын
Excellent!
@xoutaku7600 Жыл бұрын
get well bro
@rofgar Жыл бұрын
Very good guide, amazingly frustrating topic.
@letsoverengineer Жыл бұрын
The moment when you insert a voice over from another recording session x)
@jaroslavhuss7813 Жыл бұрын
Nah, this is one of the reasons why I use Nest.js - TypeScript by default, no hassle, no cry - just awesome architecture, typescript and more time for playing Witcher 3 after the work is done.
@nekony3563 Жыл бұрын
I recommend using @tsconfig/bases packages for a predefined config for you environment, so you don't have to remember what put into "target" and other properties.
@WWEK-yx1hm Жыл бұрын
CTS ???
@Novacification Жыл бұрын
Could you go over some scenarios for building and publishing. For instance, I'm creating a base server implementation (basically an express wrapper with auth middleware) and I would like to publish it to a local npm registry (Verdaccio). It publishes everything, not just the dist folder, and I'm not sure how to handle dependencies. I have some issues with importing the server package as well, needing to do a second deconstruction of the default export for the dependency. A good up to date minimal setup for building and publishing would be really cool! Something with build to dist, publish from dist and importing the package somewhere (maybe even with import instead of require)
@jacops419 Жыл бұрын
tsc --init works most of the time aswell
@eestpavel Жыл бұрын
Lately I found myself better setting vite-node rather than trying to set all that experimental flags to run my code with modern day devfeatures
@rubenheymans1988 Жыл бұрын
why not make a nestjs video? Nest is a framework for building efficient, scalable Node.js server-side applications. It uses modern JavaScript, is built with TypeScript (preserves compatibility with pure JavaScript) and combines elements of OOP (Object Oriented Programming), FP (Functional Programming), and FRP (Functional Reactive Programming).
@NH-cb2jg Жыл бұрын
copy paste dummy
@Dysfunctional704 Жыл бұрын
Can you make a video on the T3 Stack from Theo?
@shapelessed Жыл бұрын
npm init tst --init Done. Now, my way of doing this is (as a proud developer) is scripting all of this. Hosting CommonJS and ESM project templates on a NodeJS-based, fully automated file server that's using my own database that's using its own virtual file system and cloning it whenever I need. Yes It's overcomplicated for a reason don't argue just accept that life isn't always the way it should be.
@kumekster Жыл бұрын
Maybe quick guide here on how to set eslint?
@Disorrder Жыл бұрын
Or simply install nest or another boilerplate starter
@themarksmith Жыл бұрын
How about a demo on how to make a basic PWA?
@Roman-of9pl Жыл бұрын
Every time someone is sharing their project setup I recall that scene from American Psycho.
@marna_li Жыл бұрын
I went through this a couple of months ago. But there might be some starter templates. At least there should be one.
@giorgiobellisario Жыл бұрын
All these typescript problems make me solve with Vite (if Node.js required) or... Deno!
@grantdoyle1259 Жыл бұрын
2023? Getting a little ahead of ourselves aren't we?
@bensas42 Жыл бұрын
I had to do this last week haha
@Alex-hk3hr Жыл бұрын
Thanks for a great tutorial and a perfect argument why not to use JS/TS ; )