[nadawix]

This is the first visual IDE to edit React Typescript code. Even code you created outside of it.

You can run it on an existing project, and start creating pull requests to your existing code. as long as the project fits our supported technologies.

The other tools you mentioned create code, but cannot edit existing code.

This becomes a real problem when a developer changes this exported code, which causes conflicts when someone edits it in the editor.

We edit the code directly, with visual changes translated into code changes, letting developers and designers collaborate on code and through pull requests.

[preommr]

> This is the first visual IDE to edit React Typescript code. Even code you created outside of it.

tbh I find this to be misleading then. Me, and I am sure many others interested in web dev, have seen products that focus on react with a visual IDE, maybe this product is way better, but it seems like a poor first impression when I immediately think "that's bullshit" about the first thing I see.

Also how does this handle complex project setups? Like lets say i have a constant that gets injected by my bundler (e.g. webpack) that produces different results based on the environment, or middlewares? How does it display individual components when it might need to load a bunch of dependencies?

[CharlesW]

> This is the first visual IDE to edit React Typescript code. Even code you created outside of it.

Utopia had two-way sync, but that project may be in a coma. Henosia I just learned about today. It's a tough-but-important problem to solve — best of luck building a successful solution!

[benatkin]

That seems like an arbitrary standard