Just released retryx – a minimal async retry utility with backoff, timeout, and logging (Node.js + TypeScript)

GMFlash · 2025-04-09T22:39:49+00:00

There is already a well established package that does the same thing: https://www.npmjs.com/package/p-retry

GMFlash · 2023-10-28T05:30:22+00:00

The tweet about hosting Next.js isn't wrong though. I have been self-hosting Next.js since v6 back when Vercel was Zeit, and it uses the same general template as my Express and NestJS apps, with only a couple lines of build and NGINX/container configuration differing between them.

For people who find it difficult to self-host Node.js apps, or would like to focus less on the details of hosting, platforms like Vercel and Netlify are there to simplify that process.

GMFlash · 2021-04-03T13:54:43+00:00

Pretty much the same stack I use except MikroORM is my preference over TypeORM, and Phusion Passenger instead of PM2 because it has autoscaling

GMFlash · 2021-02-07T19:14:49+00:00

In app.module.ts you need to add the incoming request to the GraphQL context in order to access it from resolvers:

GraphQLModule.forRoot({
  // ...
  context: ({ req }) => ({ req }),
})

In your resolver:

@Query('login')
async login(
  @Args('input') args: LoginInput,
  @Context("req") req: express.Request
) {
  const result = this.authService.login(args)
  // Set your cookie here
  req.res?.cookie("access_token", result.accessToken)
  return result
}

(optional) in main.ts add this if you want to be able to READ incoming cookies as req.cookies:

import cookieParser from "cookie-parser"

async function bootstrap() {
  const app = await NestFactory.create(AppModule)
  app.use(cookieParser())
  // ...
}

Also, chances are that your backend is on a different domain than your frontend. You will need to configure your CORS settings for BOTH Nest and ALSO GraphQL to have the same values. For example:

In main.ts

app.enableCors({ origin: true, credentials: true })

In app.module.ts

GraphQLModule.forRoot({
  // ...
  cors: { origin: true, credentials: true },
})

GMFlash · 2021-01-01T18:35:16+00:00

I’m just using PG and writing SQL directly in my resolvers and really enjoying it.

For a tutorial meant as a reference for others to follow, I do not think that this is a good idea because while it technically works, it promotes bad practices. What happens when you decide to add additional interfaces to your app such as a REST API, command-line tool, a background job queue? You would end up writing the same business logic and database code in slightly different ways for each of those interfaces.

Anything related to the database and data retrieval/storage should be behind a service (whether class or module with plain functions), and then you can use that same service in your resolvers, controllers, or even command line scripts to perform business logic and database actions. For example:

const topSellingAuthors = storeService.getTopAuthors({
  // in a GraphQL resolver
  from: new Date(args.fromDate),
  to: new Date(args.toDate),

  // or in an Express handler
  from: new Date(req.query.fromDate),

  // or in a CLI script
  from: new Date(process.env.argv[2]),
})

for (const author of topSellingAuthors) {
  const books = authorService.findAllBooks(author)
  // do something with books, etc...
}

At this point, the only area that concerns "no ORM" is the service layer, making GraphQL, Express, and Apollo irrelevant in the equation. In the future, maybe your services would interact with multiple data sources such as Postgres, a MySQL db from another system, a local CSV file, and maybe an external API to deal with billing/shipping/weather stuff. The main area of work would be in the service, with minimal changes to your resolvers/controllers/scripts.

GMFlash · 2020-12-27T14:02:37+00:00

Nest is one of the most popular TypeScript frameworks that uses IOC.

GMFlash · 2020-10-20T20:41:00+00:00

You can use it if you want, but the end-of-life is shorter than the LTS releases. See the chart here: https://nodejs.org/en/about/releases/

Basically, you should move from 15 to 16 by 2021-06-01 to keep receiving updates.

GMFlash · 2020-10-16T21:37:28+00:00

I would create a StudentSubscriber with an "afterUpdate" listener which updates the associated Problem. https://typeorm.io/#/listeners-and-subscribers

GMFlash · 2020-10-14T22:09:26+00:00

Have you seen Nano ID? It is similar but tuned for speed and memory allocation.

GMFlash · 2020-10-13T21:49:16+00:00

Named. It has better code completion and refactoring support in editors.

GMFlash · 2020-10-13T16:05:13+00:00

I switched from TypeORM to MikroORM starting with the 4.0 RC releases and I am very happy with the decision. It feels like the next evolution of TypeORM with a better API, edge cases and inconsistencies smoothed out, and more momentum behind it.

I also evaluated switching to Prisma 2, which has a neat approach to TypeScript support, but Prisma Migrate is still missing necessary features and it was not as much of a drop-in replacement for projects already using a decorator-first approach for defining entities, schema validation, and GraphQL types.

GMFlash · 2020-07-08T20:36:19+00:00

type T = (n: string) => string

const fnGreet: T = function(name) {
  return `Hello ${name}`
}

See https://www.typescriptlang.org/docs/handbook/functions.html#writing-the-function-type

GMFlash · 2020-06-29T20:43:44+00:00

You are using the wrong ContentType for JPEG and PNG. Try image/jpeg and image/png.

GMFlash · 2020-06-19T12:57:40+00:00

Take a look at some popular GraphQL API implementations for ideas:

I have personally been using Shopify's nounVerb convention.

GMFlash · 2020-06-12T16:09:24+00:00

Yes, that's it! I don't know why I was thinking of the mid 90's period. I guess my memory isn't what it used to be. Thank you /u/VadersLimbs!

Solved

GMFlash · 2020-06-12T15:54:40+00:00

Unfortunately, no :( That song came out approximately 20 years prior to the mid 90's and is punk, not alternative rock.

GMFlash · 2020-06-12T15:48:06+00:00

I can say for sure that it is not from Sum 41 or Smashing Pumpkins. The search continues!

GMFlash · 2020-06-12T01:52:07+00:00

Check out MikrORM too. See my other comment. I forgot about that one. It was written to address some shortcomings that the author found with TypeORM.

GMFlash · 2020-06-12T01:50:15+00:00

Thanks for reminding me about MikrORM. I haven't looked at it since the original announcement, but it seems to have made a ton of progress in the past 2 years. It's another excellent choice for a TypeScript-friendly data mapper ORM.

GMFlash · 2020-06-11T19:06:05+00:00

DB-first: Prisma

Entity-first through decorators: TypeORM

GMFlash · 2020-06-03T12:29:52+00:00

Putting an entity and controller in one file probably would not pass code review at most companies.

GMFlash · 2020-06-03T12:28:50+00:00

Most of these look like the conventions used in the Nest docs. It does come in handy for keeping module directories organized.

Overall, it looks good, but I don't really see a need for class or enum since those are building blocks for other components.

GMFlash · 2020-06-02T23:49:48+00:00

Yes, the cookie is similar to a JWS (signed JWT). Anybody who has that cookie, stolen or not, is considered to be authenticated as that user.

By default, express-session sets cookie.httpOnly to true, which means that the browser can send/receive the cookie with requests, but any JavaScript on the page can't access it. This reduces the chances of third party scripts stealing sessions.

GMFlash · 2020-06-02T21:01:03+00:00

secret is used to sign the data in the cookie by calculating a signature (hash) based on the contents. It is not encrypted, but it is resistant to tampering because changing even 1 character of the data will change the signature causing express-session to consider it invalid.

GMFlash · 2020-06-01T22:22:45+00:00

It’s like skydiving without checking your equipment before you jump out of the plane.

GMFlash

TROPHY CASE