Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature]: Enable Console Ninja for Turbo Repo. #315

Open
xspaceboy opened this issue Jul 3, 2024 · 3 comments
Open

[Feature]: Enable Console Ninja for Turbo Repo. #315

xspaceboy opened this issue Jul 3, 2024 · 3 comments

Comments

@xspaceboy
Copy link

Describe the feature you'd like.

Hello, Console Ninja Developer Team!
You are making great vscode extension what I ever used.
I used this extension for Angular, Next.js, React, Node.js and TypeScript projects, and works awesome for these frameworks.
I am trying to use Console Ninja for Turbo Repo, but seems like it doesn't support yet.

@mburnell
Copy link
Member

mburnell commented Jul 3, 2024

Thank you for the kind words! We're glad you're enjoying Console Ninja!

Console Ninja does not currently support Turbopack, which is used by default by Turborepo. If you're interested in details, please see #136. However, if you're happy to use Turborepo with Webpack instead of Turbopack, Console Ninja will work for you. To use Webpack instead of Turbopack, you'll need to remove the --turbo flags from the relevant scripts in your package.json file(s). Once removed, the warning messages saying Console Ninja will not work (seen during Turborepo startup) should no longer appear, and Ninja should work correctly.

@curately
Copy link

Hi, love console ninja but not supporting turbo pack is a big headache for us. I understand some of the issues but are there realistic plans for overcoming them anytime soon?

@smcenlly
Copy link
Member

Unfortunately, we don't have plans to support Turbopack in the near future.

Console Ninja operates by intercepting file reads at the Node.js fs level to instrument console.log calls, then passing the modified file content to your development server. Since Turbopack is built in Rust and handles its own file watching and reading, as well as serving files to the browser, our ability to intercept or modify those files is extremely limited - if possible at all.

To provide a seamless experience, Turbopack would need to provide an API or similar mechanism for intercepting or modifying the file reads it performs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants