Next Development server crashes due to module and *.ts file resolution problems

[LostI77]

Summary

Next Development server crashes due to module and *.ts file resolution issues

I recently created a project with next.js and its latest version and although initially it worked correctly without any problem with the development server, I was surprised to see that this suddenly changed.

I use bun as the runtime environment for my projects.

I would like you to tell me how to solve these problems, since I have been looking for information for a while (2-3h) and I don't know where to start, I don't know if it is beyond my reach to solve it or if it is something easier to do.

Any helpful comments would be greatly appreciated.

Thx

Additional information

output from my console:


   ▲ Next.js 15.0.2 (Turbopack)
   - Local:        http://localhost:3000
   - Environments: .env.local
   - Experiments (use with caution):
     · turbo

 ✓ Starting...
(node:11304) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:2728) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

 ⚡ Million Lint v1.0.11
 ✓ Ready in 0.63ms
 ⨯ ./node_modules/@mapbox/node-pre-gyp/lib/util/nw-pre-gyp/index.html
Unknown module type
This module doesn't have an associated type. Use a known file extension, or register a loader for it.

Read more: https://nextjs.org/docs/app/api-reference/next-config-js/turbo#webpack-loaders

 ⨯ ./node_modules/fs.realpath
Unknown module type
This module doesn't have an associated type. Use a known file extension, or register a loader for it.

Read more: https://nextjs.org/docs/app/api-reference/next-config-js/turbo#webpack-loaders

 ⨯ ./src/app/lazy-animations.tsx.tsx
Module not found: Can't resolve './lazy-animations.tsx.tsx'

 ⨯ ./node_modules/@mapbox/node-pre-gyp/lib/util/s3_setup.js:76:15
Module not found: Can't resolve 'aws-sdk'
  74 |
  75 |   // if not mocking then setup real s3.
> 76 |   const AWS = require('aws-sdk');
     |               ^^^^^^^^^^^^^^^^^^
  77 |
  78 |   AWS.config.update(config);
  79 |   const s3 = new AWS.S3();



https://nextjs.org/docs/messages/module-not-found

https://nextjs.org/docs/messages/module-not-found


 ⨯ ./node_modules/@mapbox/node-pre-gyp/lib/util/s3_setup.js:43:21
Module not found: Can't resolve 'mock-aws-s3'
  41 |     // here we're mocking. node_pre_gyp_mock_s3 is the scratch directory
  42 |     // for the mock code.
> 43 |     const AWSMock = require('mock-aws-s3');
     |                     ^^^^^^^^^^^^^^^^^^^^^^
  44 |     const os = require('os');
  45 |
  46 |     AWSMock.config.basePath = `${os.tmpdir()}/mock`;
  
   ⨯ ./node_modules/@mapbox/node-pre-gyp/lib/util/s3_setup.js:112:16
Module not found: Can't resolve 'nock'
  110 |   }
  111 |
> 112 |   const nock = require('nock');
      |                ^^^^^^^^^^^^^^^
  113 |   // the bucket used for testing, as addressed by https.
  114 |   const host = 'https://mapbox-node-pre-gyp-public-testing-bucket.s3.us-east-1.amazonaws.com';
  115 |   const mockDir = process.env.node_pre_gyp_mock_s3 + '/mapbox-node-pre-gyp-public-testing-bucket';

 ✓ Compiled in 14.8s
 ✓ Ready in 17.7s
 ⨯ Error [TypeError]: Cannot read properties of undefined (reading '_handle')
    at <unknown> (file://C:\Users\Flaco\Documents\Lost\programming\projects\web\arty\.next\server\edge\chunks\node_modules_5fcb53._.js:18426:20)
    at Array.forEach (<anonymous>)
    at push.94113.module.exports (file://C:\Users\Flaco\Documents\Lost\programming\projects\web\arty\.next\server\edge\chunks\node_modules_5fcb53._.js:18425:7)
    at 56685 (file://C:\Users\Flaco\Documents\Lost\programming\projects\web\arty\.next\server\edge\chunks\node_modules_5fcb53._.js:18444:1)
    at <unknown> (file://C:\Users\Flaco\Documents\Lost\programming\projects\web\arty\.next\server\edge\chunks\edge-wrapper_e40a4b.js:693:27)
    at runModuleExecutionHooks (file://C:\Users\Flaco\Documents\Lost\programming\projects\web\arty\.next\server\edge\chunks\edge-wrapper_e40a4b.js:738:9)
    at instantiateModule (file://C:\Users\Flaco\Documents\Lost\programming\projects\web\arty\.next\server\edge\chunks\edge-wrapper_e40a4b.js:691:9)
    at getOrInstantiateModuleFromParent (file://C:\Users\Flaco\Documents\Lost\programming\projects\web\arty\.next\server\edge\chunks\edge-wrapper_e40a4b.js:624:12)
    at commonJsRequire (file://C:\Users\Flaco\Documents\Lost\programming\projects\web\arty\.next\server\edge\chunks\edge-wrapper_e40a4b.js:157:20)
    at 78746 (file://C:\Users\Flaco\Documents\Lost\programming\projects\web\arty\.next\server\edge\chunks\node_modules_@mapbox_node-pre-gyp_ebb9bb._.js:1880:13)
 ⨯ ./node_modules/@mapbox/node-pre-gyp/lib/util/nw-pre-gyp/index.html
Unknown module type
This module doesn't have an associated type. Use a known file extension, or register a loader for it.

Read more: https://nextjs.org/docs/app/api-reference/next-config-js/turbo#webpack-loaders

Try to summarize the repeated console error messages and this summarizes everything.

### Example

_No response_

[Mahfoudh94]

This is happening to me right now, everything was sound and clear and then suddenly it all started.
Weirdly enough I am using bun too, but this project I am on uses also Auth.js (formerly NextAuth) and bcrypt, my database is postgres with drizzle orm. do you happen to use any or some of these too?