Support NestJS

[Jarred-Sumner]

This is a tracking issue to get bun's node.js compatibility far enough along to support https://nestjs.com/

[DavidFencl]

+1, It would be amazing if Bun would work with NestJS.

[kenerwin88]

+1, also would love this

[jmls]

+10 please !

[michaelangeloio]

yes please!

[michaelangeloio]

this would be a game changer

[MarcStdt]

+1 would be extremely interesting !!

[muhad-bk]

Where I can start to contribute on this issue?

[ThatOneBro]

@muhad-bk We appreciate your enthusiasm! If you could try running a NestJS project in Bun and letting us know what breaks that would be extremely helpful. I'm not sure exactly sure what is missing for NestJS to work yet

[MarcStdt]

AFAIK NestJS relies on repl and the net module.
At least these two I still see marked as open in the bun roadmap.

[ammanley]

I actually was very curious about this and just got bun up and running with a fresh install of nestjs. Am toying around with a basic API, I can update as things go to see what breaks.

[piosystems]

I actually was very curious about this and just got bun up and running with a fresh install of nestjs. Am toying around with a basic API, I can update as things go to see what breaks.

I tried it too by using bun to run the distribution directly i.e. bun dist/main.js. It works for static routes. But application failed to start for more complex codes involving typeorm; concretely, a call to require('module').globalPaths along the line, erroneously returns "undefined" and aborts startup.

[piosystems]

I actually was very curious about this and just got bun up and running with a fresh install of nestjs. Am toying around with a basic API, I can update as things go to see what breaks.

I tried it too by using bun to run the distribution directly i.e. bun dist/main.js. It works for static routes. But application failed to start for more complex codes involving typeorm; concretely, a call to require('module').globalPaths along the line, erroneously returns "undefined" and aborts startup.

To be more specific, the error was within app-root-path/lib/resolve.js in node_modules, called from typeorm.

[Jarred-Sumner]

To be more specific, the error was within app-root-path/lib/resolve.js in node_modules, called from typeorm.

This error should be fixed once the canary builds (when CI is green)

To upgrade:

bun upgrade --canary

[piosystems]

To be more specific, the error was within app-root-path/lib/resolve.js in node_modules, called from typeorm.

This error should be fixed once the canary builds (when CI is green)

To upgrade:

bun upgrade --canary

The globalPaths issue has been fixed. Thank you. Next blocker is lack of http2 implementation by bun. Is http2 support roadmapped yet?

[devongermano]

If you want to build and run your project with Bun, you can:

bun upgrade --canary

package.json:

"start:dev": "nest start --watch --exec \"bun run\"",

nest-cli.json :

"entryFile": "main.js"

^{(bun didn't like being passed a script without a file extension)}

[mlazuardy]

@devongermano
it worked quite well using nest start --watch --exec \"bun run\" but when running

bun dist/main.js

it return http2 error ( i think its related to my project package somwhere)

Cannot find package "http2" from "/myprojectdir/node_modules/@aws-sdk/node-http-handler/dist-cjs/node-http2-handler.js"

[krisanalfa]

I think Bun supports Nest.js. I made a simple repro repo here. Though it's a very minimal repo, but it's able to proof that it is possible to use Nest.js with Bun.

[ntheanh201]

I think Bun supports Nest.js. I made a simple repro repo here. Though it's a very minimal repo, but it's able to proof that it is possible to use Nest.js with Bun.

I forked your repo and tried to integrate with Mongoose but it didn't work. I think we still need to wait quite a lot of time until we can use it in production

[DavidFencl]

My experience so far is same as @ntheanh201 says. Unless your app is super simple you will probably get compatibility issues with libs like Mongoose or TypeORM.

[fangzq229]

wait

[ghost]

Hi folks, what do we need to make the bun compatible with nestjs?

[oishiimendesu]

My experience so far is same as @ntheanh201 says. Unless your app is super simple you will probably get compatibility issues with libs like Mongoose or TypeORM.

This week, I will try using prisma and i'll bring my feedback about it.

[minhaics]

hope nestjs support natively for bun runtime.

[ali-habibzadeh]

Please put in in a bun!

[gabriiels]

Has anyone done a test with version 0.6?

[elix1er]

Has anyone done a test with version 0.6?

doing this now, 0.6.3 // canary

[mlazuardy]

When running nest start --watch --exec \"bun run\"

it return missing script /dir/dist/main

does bun / nestjs need to explicitly use file type (js,ts) ?

[tronicboy1]

I have tested this in 0.6.3 and I see Bun appears to be having a problem setting the emitDecoratorMetadata setting. Injected services are undefined in the controller.

Anyone have any ideas on what we can do?

[Nest] 8956  - 05/25/2023, 7:10:01 AM   ERROR [ExceptionsHandler] undefined is not an object (evaluating 'this.appService.getHello')
getHello@/Users/austin/Documents/practice/bun-quickstart/src/app.controller.ts:12:57

[DavidFencl]

I can't speak for a larger more fully featured repo as I have not had time flesh this out. But I recently put together a small little toy repo (https://github.com/Scalahansolo/bun-nest) that has the api in this repo both running and building using bun. It also uses bun as the package manage. If people are interested, I could continue to flesh this out with something like Drizzle.

Honestly I think @Jarred-Sumner and the team should close this issue out. At this point Bun properly supports decorators and things are working. If people run into more specific isolated issues that can be repoed, they should open up new issues with reproductions for the bun team to track down.

+1 on this. I have similar experience. Bun works with Nest itself now, which is exciting! It has issues with libs like mongoose, but that's not a direct Nest issue anymore.

[Jarred-Sumner]

NestJS works in Bun. I will go ahead and close this out. If you continue to run into more issues, please file a new issue in Bun's repo for the more specific library that isn't working as expected.

Error compiling schema, function code: const schema16 = scope.schema[10];return function validate14(data,

@SOG-web that stacktrace is showing that it is running in Node.js (not Bun)

SyntaxError: Import named 'FileUpload' not found in module '/home/tuan-dd/repos/booking-api/node_modules/bull/index.js'.

@tuan-zigvy please try using import {type FileUpload} from '... to tell Bun that it is a TypeScript type and not to throw an error if the import doesn't exist at runtime.

[undefineduz]

+1, It would be amazing if Bun would work with NestJS :)

[Jarred-Sumner]

+1, It would be amazing if Bun would work with NestJS :)

@undefineduz what issue are you running into? Please file a new issue and include the error message + some steps to reproduce it. NestJS works in Bun, but there could be libraries which NestJS or your application depends on which do not fully work in Bun yet.

[NarHakobyan]

@Jarred-Sumner You are doing amazing work. congrats 🎉.

do you have plans to implement async_hooks?

[Jarred-Sumner]

@Jarred-Sumner You are doing amazing work. congrats 🎉.

do you have plans to implement async_hooks?

async_hooks is largely implemented (AsyncLocalStorage) - what is missing that you're using?

[NarHakobyan]

I just tried to migrate nestjs boilerplate to bun, but got warning and error.

[bun] Warning: async_hooks.createHook is not implemented in Bun. Hooks can still be created but will never be called. error: Cannot find module "typeorm/util/StringUtils" from "/Users/narekhakobyan/Desktop/projects/awesome-nest-boilerplate/src/snake-naming.strategy.ts"

[iiian]

I think Bun supports Nest.js. I made a simple repro repo here. Though it's a very minimal repo, but it's able to proof that it is possible to use Nest.js with Bun.

With bun@1.0.19 which just recently released (thanks!) if you:

1. install @nestjs/swagger@^7.1.17
2. update the index.ts's first @Get() route to be:

@Get('/:my_route_param')
public index(
  @Param('my_route_param') my_route_param: string
) {
  // whatever
}

Then when you run index.ts @Param() annotation causes crash:

[Nest] 80972  - 12/23/2023, 11:53:24 PM     LOG [NestFactory] Starting Nest application...
[Nest] 80972  - 12/23/2023, 11:53:24 PM     LOG [InstanceLoader] AppModule dependencies initialized +20ms
 9 | class ParameterMetadataAccessor {
10 |     explore(instance, prototype, method) {
11 |         const types = Reflect.getMetadata(constants_1.PARAMTYPES_METADATA, instance, method.name);
12 |         const routeArgsMetadata = Reflect.getMetadata(constants_1.ROUTE_ARGS_METADATA, instance.constructor, method.name) || {};
13 |         const parametersWithType = (0, lodash_1.mapValues)((0, reverse_object_keys_util_1.reverseObjectKeys)(routeArgsMetadata), (param) => ({
14 |             type: types[param.index],
                       ^
TypeError: undefined is not an object (evaluating 'types[param.index]')

Here's the full example:

import { Controller, Get, Module, Logger, Param } from '@nestjs/common';
import { NestFactory } from '@nestjs/core';
import { SwaggerModule, DocumentBuilder } from '@nestjs/swagger';

@Controller()
class AppController {
  @Get('/:param')
  public index (
    @Param('param') param: string // <--- Still problematic.
  ) {
    return {
      message: 'Hello World!',
      date: new Date(),
    };
  }
}

@Module({
  controllers: [AppController],
})
class AppModule {}

async function main () {
  const app = await NestFactory.create(AppModule);
  const document = SwaggerModule.createDocument(app, new DocumentBuilder().build());
  SwaggerModule.setup('docs', app, document);
  await app.listen(3000);
  Logger.log('Server started on http://localhost:3000', 'NestApplication');
}

main();

autogenerating swagger docs is super important if you want auto-generated type-safe clients with something like openapi-generator.

[dylan-conway]

@iiian do you have emitDecoratorMetadata: true in your tsconfig.json? Looks like swagger needs decorator metadata enabled for the Param() decorator, and the simple repo doesn't have it enabled the tsconfig

[iiian]

That fixed it, nice! 🚢 🇮🇹

[hedaukartik]

Anyone tried bun run src/main.ts --watch --hot in place of nest start --watch?
Its gives me multiple errors on startup related to cookieParser and prisma.

TypeError: cookieParser is not a function.

[GerbenRampaart]

@Jarred-Sumner I think this ticket should be re-opened, bun test doesn't work with a nestjs project and starting the project with the vscode debugger has the same result.

In both cases it injects undefined dependencies.

[Scalahansolo]

Nest + Bun work fine. I just tested my example repo at https://github.com/Scalahansolo/bun-nest and things still work well on bun 1.1

If your experiencing other issues, it's more likely an issue with some other lib.

[GerbenRampaart]

Nest + Bun work fine. I just tested my example repo at https://github.com/Scalahansolo/bun-nest and things still work well on bun 1.1

If your experiencing other issues, it's more likely an issue with some other lib.

Thanks, interesting repo. It doesn't seem to contain any tests, which was what I mentioned. I'll clone it and see what the differences are with my solution. I'll also add the .vscode/launch to your repo and see if I get the same error as with bun test.

I have gotten nest apis to work no problem, but specifically with running in debug mode and bun test I get undefined injectables.

[Scalahansolo]

That may be true, but in that case I think a new issue to track that specific issue would be good. More noise here isn't going to help the bun team.

[NarHakobyan]

It’s nor working with my basic boilerplate project

[elovin]

Basically bun does not seem to work with any serious (larger) NestJS Application since there are a lot of issues / bugs with decorators which are used a lot in NestJS (guards, controllers, interceptors, pipes, filters, swagger ....) and its dependencies (e.g. class-validator, class-transformer, mongoose, typeorm ...).

It seems to boil down to issues/bugs with emitDecoratorMetadata which behaves differently with bun compared to node and thus as long as that is the case it is not a drop in replacement for node.

[GerbenRampaart]

That may be true, but in that case I think a new issue to track that specific issue would be good. More noise here isn't going to help the bun team.

Turns out it's not noise. After lots of digging it was this open issue: #2927

I get the same undefined injectables with the dreaded 'Cannot access uninitialized variable' in nestjs.

I think the decorator support is too buggy, but I can't find the exact line. So I think your statement 'Nest + Bun works fine' is a stretch.

As I said earlier, your example repo is a really nice workspaces example though, so thanks, I copied some of it's approaches.

[birkskyum]

NestJS works in Bun. I will go ahead and close this out. If you continue to run into more issues, please file a new issue in Bun's repo for the more specific library that isn't working as expected.

The ask from Jarred is that we create new tickets for every problem with NestJS, to stay organized. I guess this ticket can still be linked, so it's easy to find things from here too, like this mentioned issue:

• ReferenceError: Cannot access uninitialized variable #2927

[GerbenRampaart]

NestJS works in Bun. I will go ahead and close this out. If you continue to run into more issues, please file a new issue in Bun's repo for the more specific library that isn't working as expected.

The ask from Jarred is that we create new tickets for every problem with NestJS. I guess this ticket can still be linked, so it's easy to find things from here too.

I sure get that. The problem (for me) is that I don't have enough information for creating the ticket. I have a non-working nestjs app that sometimes fails with this error. Then it's better when I restart, it seems, and then sometimes not.

The only useful data I have is the fact that it only happens in my nestjs apps, and nowhere else. So I'm not sure where to indicate it other than here.

[birkskyum]

@GerbenRampaart , can you i.e. make a 'nest fails to run in bun' with repro steps, or mention that it's flaky in your case and crash frequency/type of app you have, and with your environment and what you see?

[GerbenRampaart]

@GerbenRampaart , can you i.e. make a 'nest fails to run in bun' with repro steps, or mention that it's flaky in your case and crash frequency/type of app you have, and with your environment and what you see?

Pushed all changes in my public repo and created this ticket: #10116

You should be able to reproduce by just cloning and running bun test.

Other than that I haven't got a clue yet.

[NarHakobyan]

@GerbenRampaart , can you i.e. make a 'nest fails to run in bun' with repro steps, or mention that it's flaky in your case and crash frequency/type of app you have, and with your environment and what you see?

Hey, here is the boilerplate which we are trying to adapt bun

https://github.com/NarHakobyan/awesome-nest-boilerplate

[dotdevpro]

@GerbenRampaart , can you i.e. make a 'nest fails to run in bun' with repro steps, or mention that it's flaky in your case and crash frequency/type of app you have, and with your environment and what you see?

Hey, here is the boilerplate which we are trying to adapt bun

https://github.com/NarHakobyan/awesome-nest-boilerplate

Probably may be because of cls-hooked, i have similar issue with bun/nest/typeorm/typeorm-transactional, if i use @transactional() decorator with bun i have this error:

ERROR [ExceptionsHandler] No context available. ns.run() or ns.bind() must be called first.
Error: No context available. ns.run() or ns.bind() must be called first.
    at set (/server/node_modules/cls-hooked/context.js:38:14)

[NarHakobyan]

@GerbenRampaart , can you i.e. make a 'nest fails to run in bun' with repro steps, or mention that it's flaky in your case and crash frequency/type of app you have, and with your environment and what you see?

Hey, here is the boilerplate which we are trying to adapt bun

https://github.com/NarHakobyan/awesome-nest-boilerplate

Probably may be because of cls-hooked, i have similar issue with bun/nest/typeorm/typeorm-transactional, if i use @transactional() decorator with bun i have this error:

ERROR [ExceptionsHandler] No context available. ns.run() or ns.bind() must be called first.

Error: No context available. ns.run() or ns.bind() must be called first.

    at set (/server/node_modules/cls-hooked/context.js:38:14)

If you try to run the project using bun, then it will start giving errors on interface files like they don't exist

[kongxiangyiren]

bun install @grpc/grpc-js  @grpc/proto-loader @nestjs/microservices @nestjs/platform-socket.io amqp-connection-manager  class-transformer  class-validator ioredis kafkajs  mqtt  nats -D