feat: Add NestJS adapter

[blaine-arcjet]

This adds a NestJS adapter to our SDK. It is definitely just a first implementation while we wait for feedback from users.

NestJS is a very different framework than adapters for previous frameworks, but I tried to make it feel natural for users of NestJS. This includes the ArcjetModule export which they can import into their @Module decorators, the ArcjetGuard export which can be used with @UseGuards(ArcjetGuard), and the @WithArcjetRules decorator which can provide additional rules to the ArcjetGuard that is run before the handler.

Unlike previous adapters, the design of NestJS doesn't allow us to leverage our type inference to help guide users, so we rely more heavily on runtime errors if things are misconfigured, such as trying to use a validateEmail rule with ArcjetGuard.

One benefit of the adapter is that we support NestJS on top of both Express and Fastify!

I've revamped the NestJS example to highlight various ways the adapter can be used and even created a NestJS + Fastify example to ensure we work with both.

Closes #781

[trunk-io]

😎 Merged successfully - details.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@nestjs/common@10.4.4	None	+4	601 kB	nestjscore
npm/@nestjs/core@10.4.4	Transitive: environment, filesystem, network, shell	+27	1.72 MB	nestjscore
npm/@nestjs/platform-fastify@10.4.4	Transitive: environment, eval, filesystem, unsafe	+61	8.33 MB	kamilmysliwiec, nestjscore
npm/nestjs-fastify@0.0.1	None	0	0 B
npm/nestjs-launchdarkly@0.0.1	None	0	0 B
npm/nestjs@0.0.1	None	0	1.02 kB	quangv

🚮 Removed packages: npm/@nestjs/common@10.4.2, npm/@nestjs/core@10.4.2, npm/@nestjs/platform-express@10.4.2, npm/@nestjs/testing@10.4.2, npm/@types/jest@29.5.13, npm/@types/supertest@6.0.2, npm/nest-js@0.0.1, npm/supertest@7.0.0, npm/ts-jest@29.2.5, npm/ts-loader@9.5.1, npm/ts-node@10.9.2

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/fast-content-type-parse@1.1.0, npm/light-my-request@5.13.0, npm/fast-json-stringify@5.16.1, npm/avvio@8.4.0

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

[blaine-arcjet]

@SocketSecurity ignore npm/fast-content-type-parse@1.1.0
@SocketSecurity ignore npm/light-my-request@5.13.0
@SocketSecurity ignore npm/fast-json-stringify@5.16.1
@SocketSecurity ignore npm/avvio@8.4.0

All fastify packages.

[blaine-arcjet]

We should consider using https://docs.nestjs.com/fundamentals/execution-context#current-application-context to make sure we're in an http context but let's wait for user feedback.

[blaine-arcjet]

I've added an example that uses LaunchDarkly to configure the rules at NestJS application startup. This demonstrates that the ArcjetModule can be configured via async logic by using ArcjetModule.forRootAsync with a class/factory/etc.

[davidmytton]

Great to see these examples!