Artem Govorov

Try setting the node path for wallaby in your Atom init script as [described in the docs](https://wallabyjs.com/docs/intro/install.html#nodejs-1). You may also try [this suggestion](https://wallabyjs.com/docs/intro/get-started-atom.html#comment-2657361685). Could you please also open Atom Dev...

Unfortunately we can't reproduce the issue locally. Please try re-installing the package and if it doesn't help - try running Wallaby with other packages disabled to see if something else...

Thanks for posting the feature request. We'll be addressing some of the points when implementing the [debugger support feature](https://github.com/wallabyjs/public/issues/74), so feel free to subscribe to it. > console.log output often...

When TSX files are compiled by TypeScript, the default option is to preserve JSX fragments inside them. Node doesn't understand JSX syntax, so you need to [use `jsx: 'react'` option...

@tomitrescak I'm trying to reproduce the issue you have mentioned and commenting out the ``` import { Component } from "react"; ``` line in [newpost.tsx](https://github.com/mantrajs/kickstart-mantrajs-webpack-typescript/blob/master/src/client/modules/core/components/newpost.tsx#L1), but with or without it,...

@tomitrescak Same for the `postlist.tsx`, works with or without `import { Component } from "react";`. The imported `Component` is not used anywhere inside the `postlist.tsx`, so I don't see a...

Could you please create and share a sample Github repo where we can reproduce the issue? It's enough if you just put your package.json, wallaby config and one simple test...

It's by design in all editors that we support for a few reasons: - we still need to truncate the message (and we do), so to see the full message...

Unfortunately we can't reproduce the issue locally with the same Atom/OS version. It looks like some of the other packages you have installed may be affecting the plugin. Please try...

I understand there's the shortcut conflict, but wallaby had been using the shortcut since day one, so changing it may affect a lot of users. I'll leave the issue open...