onur-ozkan/nestjs-enlighten

laravel-ignition like error page for NestJS Framework

nestjs-enlighten's Issues

UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open 'internal/process/task_queues.js'

When installing and enabling enlighten using the information in the readme, I get this on the console:

(node:29011) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open 'internal/process/task_queues.js' at Object.openSync (fs.js:465:3) at Object.readFileSync (fs.js:368:35) at /Users/yyy/Projekte/xxx/backend/node_modules/nestjs-enlighten/src/Services/Resolver/stack-resolver.ts:18:20 at Array.map (<anonymous>) at StackResolverService.getProperErrorStack (/Users/yyy/Projekte/xxx/backend/node_modules/nestjs-enlighten/src/Services/Resolver/stack-resolver.ts:16:20) at processTicksAndRejections (internal/process/task_queues.js:93:5) at ViewCompilerService.getCompiledView (/Users/yyy/Projekte/xxx/backend/node_modules/nestjs-enlighten/src/Services/ViewCompiler/view-compiler.service.ts:23:36) at emitUnhandledRejectionWarning (internal/process/promises.js:168:15) at processPromiseRejections (internal/process/promises.js:247:11) at processTicksAndRejections (internal/process/task_queues.js:94:32) (node:29011) Error: ENOENT: no such file or directory, open 'internal/process/task_queues.js' at Object.openSync (fs.js:465:3) at Object.readFileSync (fs.js:368:35) at /Users/yyy/Projekte/xxx/backend/node_modules/nestjs-enlighten/src/Services/Resolver/stack-resolver.ts:18:20 at Array.map (<anonymous>) at StackResolverService.getProperErrorStack (/Users/yyy/Projekte/xxx/backend/node_modules/nestjs-enlighten/src/Services/Resolver/stack-resolver.ts:16:20) at processTicksAndRejections (internal/process/task_queues.js:93:5) at ViewCompilerService.getCompiledView (/Users/yyy/Projekte/xxx/backend/node_modules/nestjs-enlighten/src/Services/ViewCompiler/view-compiler.service.ts:23:36) (node:29011) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. at emitDeprecationWarning (internal/process/promises.js:180:11) at processPromiseRejections (internal/process/promises.js:249:13) at processTicksAndRejections (internal/process/task_queues.js:94:32) (node:29011) UnhandledPromiseRejectionWarning: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string or an instance of Buffer or URL. Received null at Object.openSync (fs.js:457:10) at Object.readFileSync (fs.js:368:35) at /Users/yyy/Projekte/xxx/backend/node_modules/nestjs-enlighten/src/Services/Resolver/stack-resolver.ts:18:20 at Array.map (<anonymous>) at StackResolverService.getProperErrorStack (/Users/yyy/Projekte/xxx/backend/node_modules/nestjs-enlighten/src/Services/Resolver/stack-resolver.ts:16:20) at processTicksAndRejections (internal/process/task_queues.js:93:5) at ViewCompilerService.getCompiledView (/Users/yyy/Projekte/xxx/backend/node_modules/nestjs-enlighten/src/Services/ViewCompiler/view-compiler.service.ts:23:36) at emitUnhandledRejectionWarning (internal/process/promises.js:168:15) at processPromiseRejections (internal/process/promises.js:247:11) at processTicksAndRejections (internal/process/task_queues.js:94:32) (node:29011) TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string or an instance of Buffer or URL. Received null at Object.openSync (fs.js:457:10) at Object.readFileSync (fs.js:368:35) at /Users/yyy/Projekte/xxx/backend/node_modules/nestjs-enlighten/src/Services/Resolver/stack-resolver.ts:18:20 at Array.map (<anonymous>) at StackResolverService.getProperErrorStack (/Users/yyy/Projekte/xxx/backend/node_modules/nestjs-enlighten/src/Services/Resolver/stack-resolver.ts:16:20) at processTicksAndRejections (internal/process/task_queues.js:93:5) at ViewCompilerService.getCompiledView (/Users/yyy/Projekte/xxx/backend/node_modules/nestjs-enlighten/src/Services/ViewCompiler/view-compiler.service.ts:23:36)

Besides this, it seems that the stack displayed on the error page is wrong - or not complete at least.

Blank screen with console errors

Hi 👋 I was trying to test out this package, but I ran into these console errors:

I copied and pasted from the readme, ran npm run start:dev, and added throw new Error('sanity') in my code. I’m running "@nestjs/common": "^7.0.0", and "nestjs-enlighten": "0.0.5-beta".

I really like the idea though, would love to see it working 😄 maybe I missed a step or something

npm install does not install dist directory

When installing 0.0.7-beta, the dist folder is missing in the package. Therefore, the module does not work.
When installing the previous version (npm install [email protected]), everything is fine.

Probably, there is something wrong with the build process.

I hope, I did not break something with my PR from yesterday.

'statusCode' is undefined in Services/Errors/error.service.js

Hi,

I recently installed enlighten in my API and everything stopped working when an error occurs. I was wondering that something could be wrong with my API, so I installed enlighten on a newly created NestJS API and the results were the same. I couldn't fix this problem myself, so I'm here asking for your help, I'll leave the problem stack below

(node:5252) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'statusCode' of undefined
    at ErrorService.errorDeterminator (/home/mokyunnetwork/Gitlab/nestjs-api/node_modules/nestjs-enlighten/dist/Services/Errors/error.service.js:10:55)
    at ViewCompilerService.getCompiledView (/home/mokyunnetwork/Gitlab/nestjs-api/node_modules/nestjs-enlighten/dist/Services/ViewCompiler/view-compiler.service.js:16:78)
    at ExceptionFilter.catch (/home/mokyunnetwork/Gitlab/nestjs-api/node_modules/nestjs-enlighten/dist/Filters/exception.filter.js:31:77)
    at ExceptionsHandler.invokeCustomFilters (/home/mokyunnetwork/Gitlab/nestjs-api/node_modules/@nestjs/core/exceptions/exceptions-handler.js:33:26)
    at ExceptionsHandler.next (/home/mokyunnetwork/Gitlab/nestjs-api/node_modules/@nestjs/core/exceptions/exceptions-handler.js:13:18)
    at /home/mokyunnetwork/Gitlab/nestjs-api/node_modules/@nestjs/core/router/router-proxy.js:24:35
    at Layer.handle_error (/home/mokyunnetwork/Gitlab/nestjs-api/node_modules/express/lib/router/layer.js:71:5)
    at trim_prefix (/home/mokyunnetwork/Gitlab/nestjs-api/node_modules/express/lib/router/index.js:315:13)
    at /home/mokyunnetwork/Gitlab/nestjs-api/node_modules/express/lib/router/index.js:284:7
    at Function.process_params (/home/mokyunnetwork/Gitlab/nestjs-api/node_modules/express/lib/router/index.js:335:12)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:5252) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:5252) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Node version: v14.4.0
NestJS version: 7.4.1
Enlighten version: 0.0.4-beta