You need to provide some classes and decorators yourself to maintain the same style as typeorm@2.x
.
@EntityRepository(UserEntity)
export class UserRepository extends Repository<UserEntity> {}
↓
import got, { HTTPError, Method, Options } from "got/dist/source"; | |
import * as fs from "fs"; | |
import FormData from "form-data"; | |
const gotExtended = got.extend({ | |
hooks: { | |
beforeRetry: [ | |
(options, error, retryCount) => { | |
console.log("beforeRetry", retryCount); | |
}, |
class WindowCounter { | |
private windowSize: number; // Window size in seconds | |
private counter: Map<number, number>; // Map to store request counts | |
private timer: any; // Timer reference | |
constructor(windowSize: number) { | |
this.windowSize = windowSize; | |
this.counter = new Map(); | |
this.timer = null; | |
} |
There are several ways of mounting a Nest application. You can create a web app, a microservice or just a bare Nest standalone application (without any network listeners). The Nest standalone application is a wrapper around the Nest IoC container, which holds all instantiated classes. We can obtain a reference to any existing instance from within any imported module directly using the standalone application object. Thus, you can take advantage of the Nest framework anywhere, including, for example, scripted CRON jobs. You can even build a CLI on top of it.
To create a Nest standalone application, use the following construction:
@@filename()