tsdx VS apollo-server

tsdx - Zero-config CLI for TypeScript package development

If you’re into TypeScript, I highly recommend https://tsdx.io . I’ve used it to create a package before and it’s so much easier

Thanks for the insight fellas. Aside question, I was thinking of bootstrapping the project with tsdx, but their last release was well over 2 years ago. Wondering if there are any alternative options for creating libraries?

NOTE: If your project uses TypeScript, I would suggest using tsdx instead.

Sadly, it's a bit dead. We switched to dts-cli fork, but tsup looks good too

I don't depend on the actual typescript docs much but thankfully in @types and in tons of repos there are examples of well written typescript code.

The amount of JS and TS out there is also a bit of a foot gun though so stick with heavily used/starred libs if you aren't sure.

One tool that helps a lot with developing libraries in typescript is TSDX[0] or its successor dts-cli[1] and there is a bunch of good stuff in awesesome-typescript[2].

Maybe library devving is harder?(more work?) with tyepscript but it is worth it for the end developer, especially if that end developer is you. If you aren't using your own libs then you're probably getting paid by someone else to make them or... idk.

https://github.com/jaredpalmer/tsdx

We will use a TSDX library - this tool is something similar to create-react-app, but for creating components library. It allows as to initialize a project immediately with already set up bundler, Rollup with Typescript supporting, testing with Jest, code formatter, Prettier and Storybook.

May be you need to try https://tsdx.io/

So what is the ideal way to build TypeScript libraries? I've heard that tsdx https://tsdx.io/ is quite good

There’s tsdx. But I’d recommend using Vite and storybook-vite

Another interesting point is that executing fetches on the server can allow developers to more easily leverage caching. Next.js already handles caching out-of-the-box and I’m curious to see if the wider adoption of RSC reduces the need to combine React with solutions like Apollo Server and Apollo Client. While there are other benefits to these tools, RSC could provide similar caching behavior without the need to invest in a GraphQL solution.

There are several GraphQL server implementations, however, for this tutorial, we'll utilize Apollo GraphQL's Apollo Server, a lightweight and flexible JavaScript server that makes it easy to build GraphQL APIs.

As I mentioned, their main GraphQL server package is[1], so that's where the confusion came from. Thanks.

[1] https://github.com/apollographql/apollo-server/blob/9817bc47...

While working on this blog post, I learned that Apollo Server, the most popular GraphQL server for typescript, uses a similar method for adding error codes to GraphQL. It even lets you add custom errors. Hopefully, someday other GraphQL server projects will follow them. Until then, we’ve got a strong indication we took the right approach.

GraphQL is just a schema, there are many different implementations of a GraphQL server, AppSync being one of them. I mentioned Apollo server in this series as well.

After some head-scratching, I opened an issue on Apollo Server’s GitHub repository. There, Apollo Server contributor @​glasser shared a helpful suggestion: why not invoke our AuthPlugin from Apollo Server’s context function? Throwing from context would ensure we can control the HTTP status response without having to introduce more methods and error checks to our AuthPlugin (like unexpectedErrorProcessingRequest). With that suggestion in mind, we rewrote our AuthPlugin as follows:

Apollo as a middleware in Express.js, actually.

Apollo Server 3 Cookie Issue #5775

Lastly, instead of writing our API core ourselves, we'll be using the star of this episode --- Apollo Server (a.k.a. GraphQL server). It has detailed documentation available here.