[BUG] Source maps missed in the package

[diarmind]

• [.] I've read the docs of nestjs-pino
• [.] I've read the docs of pino and pino-http
• [.] I couldn't find the same open issue of nestjs-pino
• [.] This bug is related only to current library or I've tested the same behaviour with the built-in logger and this is not a bug of NestJS.

What is the current behavior?

Files into nextjs-pino package point to source maps with source mapping url comments. For example //# sourceMappingURL=LoggerErrorInterceptor.js.map in node_modules/nestjs-pino/LoggerErrorInterceptor.js.
There is no .map.js files exist in the package.
Compiling server with webpack with an option "devtool": "source-map" and source-map-loader results in warnings

Failed to parse source map from '<your-app-path>/node_modules/nestjs-pino/InjectPinoLogger.js.map' file: Error: ENOENT: no such file or directory, open '<your-app-path>/node_modules/nestjs-pino/InjectPinoLogger.js.map'

What is the expected behavior?

.js.map files are included in the package. source-map-loader is able to locate source maps.

Please provide minimal example repo, not code snippet. Without example repo this issue will be closed.

Will make an example in days.

Please mention other relevant information such as Node.js version and Operating System.

Not specific to the environment.

[iamolegga]

@diarmind so, the solution here is just to ship source maps in the npm package as well, right?