You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As best as we can tell, prior to [email protected], webpack was being used to compile your files, which in turn meant that Console Ninja would detect and process your project files. By default, the latest version of nest uses TypeScript instead of webpack, but you can tell it to explicitly use webpack via the CLI.
In your sample project, you are able to use Console Ninja if you run your dev tools with yarn start:dev -- --webpack.
We've now added first class support for Nest.js projects to address this issue. If you update to Console Ninja v1.0.239, it will work for you.
Unfortunately this isn't something that we are able to support right now. The way nest builder works with SWC is that SWC takes control of compiling your application to your dist folder. Since SWC is written in rust and runs in a separate process, Console Ninja doesn't have the opportunity to intercept and add its logging / processing.
What happened?
After several updates in the past month, it stopped working in Nest.JS and there is no log in the output anymore.
Version
1.0.238
Steps to reproduce (or sample repo)
nest new console-ninja-test
.console.log('test')
insideapp.service.ts
before the linereturn 'Hello World!';
.yarn start:dev
.localhost:3000
. (default port is 3000).Hello World!
in response as a string, andtest
will log in to whatever terminal you used to run the app.Log output
The text was updated successfully, but these errors were encountered: