It is going to be a very competitive market but you still have a chance if you serve the needs of professional React development. Unlike POC and MVP projects by people who are learning React, professional React projects that serve production are very complex. Developers need to deliver features without regression, debug with whatever tools they have to find out root cause and fix the bug without causing regression and more issues. Tight unit tests, integration tests and QA cycles.

I have been using Cursor + Claude (Composer) in production code base with some success. Integrations with live React DevTools in the browser could make UI debugging and iterative development much faster. But you also need to think outside of the box of IDE. It is never about IDE. It is about high quality workflow.

▲

jsunderland323 9 hours ago | parent [-]

>you still have a chance if you serve the needs of professional React development

That's my entire thesis. I think it's a long long road. But I think you've actually done a great job of pretty much seeing the whole vision.

▲

ontouchstart 9 hours ago | parent [-]

That is why Playwright might be a critical piece of the puzzle instead of good to have.

I have instructed agent to generate Playwright test from screenshots that will dump API calls to debug and generate mocks to trigger the edge cases bugs. I am sure if jstool is there, it can fix the bug and reload.

▲

jsunderland323 9 hours ago | parent [-]

To be clear, I'm with you 100%. You have my word that I will add in playwright when we get to a point where we can support it.

	▲	ontouchstart 9 hours ago \| parent [-]
		If you can build browser automation into jsxtool, perhaps it can replace playwright. If I remember correctly, the guys who developed puppeteer/playwright used to work for chrome devTools or something.