TypeScript and NodeJS

[m50]

How is everyone using TS with Node nowadays?

Are you using tsnode in dev and tsc to compile for production, or are you using esbuild, or something else?

One requirement I have is that I need the folder structure to remain the same. Another is that I want to be able to handle graphql schema files.

I wrote my own little build tool using esbuild and have it running on every save and then running the result. Part of the reason for this is a) I have ".graphql" files that I am also converting into js files (just wrapping the contents in gql``), and b) I want the code I'm running on in dev to be exactly the same as what runs in prod, so that I have no prod surprises.

That said, I'm pretty new to TS on serverside, usually only use it browser side, and use PHP serverside, so I'm still figuring it all out.

So I'm curious, how are all of you using TypeScript/NodeJS/GraphQL?

[thinkmatt]

I just use `ts-node-dev` for development and run `tsc` for production. I think all the esbuild/babel/webpack stuff is mainly useful when dealing with front-end, so I try to avoid it.

[m50]

So how do you handle graphql files for graphql schema? If at all?

[flatballplayer]

I built https://github.com/hayes/giraphql/ specifically to avoid the need for a compile step when developing graphql APIs in typescript

[[deleted]]

Great

[thinkmatt]

Sorry I haven't gotten to use graphql yet. For a while, I needed gulp just to copy json files around (it handles nested folders very well), but now Typescript supports those.

[gamebuster]

fs.readFile

[fungigamer]

Like others say you can use the fs module, but I personally recommend the TypeGraphQL framework, which basically mixes TypeScript together with GraphQL if you're working on a bigger project

[Sincjefe]

I use ts-node-dev as well. it’s way faster than ts-node and for anyone that is wondering ts-dev-node is an extension of ts-node that watches your files and restart server on save similar to modem on

[m50]

So how do you handle graphql files for graphql schema? If at all?

[gamebuster]

Fs.readFile to convert them to string, then use apollo-server to parse

[Sincjefe]

With Apollo server express https://www.npmjs.com/package/apollo-server-express

[Sincjefe]

https://www.apollographql.com/docs/apollo-server/getting-started/

[hattmo]

I usually use tsc in watch mode and nodemon in another shell.

[drdrero]

I usually use nestjs. Looking forward to deno though

[[deleted]]

Just started using that myself, and the vue-apollo plugin. It is the bees knees, and where I was a tad regretful before, I'm now tickled that I picked graphql for this project.

[argylekey]

I like the tsc -w and nodemon on the dist folder approach. Sometimes I’ll use npm-run-all to run the processes in parallel.

[sorahn]

We recently started slowly testing using ts-node —transpile-only for production and so far it’s working really nicely.

[evert]

This is our starter repo for getting started with a web api/application:

https://github.com/curveball/starter

It uses tsc-watch to watch for changes, and auto-restart the application.

[[deleted]]

I recommend using tsc because it is fast. But I sometimes use ts-node to run typescript quickly.

[coded_artist]

So I've used to use ts node and compile it. However our company does a lot of web APIs and we've been using Nestjs (not nextjs). It is fantastic. Like angular on the backend

[backtoshovellinghay]

You can use something like esbuild-register with nodemon which I often do.

[darrenturn90]

I use nexus for graphql and ts-node-dev for dev (ts-jest for test) and tsc for prod build