Component not running properly with now-cli develop, only works on instance

[Devin V_]

I am making the counter custom component example from the developer site: dev site counter component

My component ONLY works in my instance, but NOT when I am use now-cli develop

When I use the now-cli develop, it will open the component but never set the initial state or allow for me to select the buttons.

The now-cli develop will continue to update the app properly if I make any changes, but I still have the same issue where not initial state is set and the buttons are unclickable.

Here is the same component on my instance:

EDIT:
So the VM30:2 error also happens when I am just setting up the now-cli scaffolding, and I am still unable to click a simple button element.

This implies it has nothing to do with the index.js

[Community Alums · Accepted solution]

Hi Devin,

1) Add "react-error-overlay": "6.0.9" into your package.json file, inside devDependencies

2) Run npm i --save-dev react-error-overlay@6.0.9 from your project folder.

This should solve your purpose.

Thanks,

Kush

[Devin V_]

Thank you, this resolved my issue.

To give everyone who finds this post some more background, there is an iframe the overlays the whole app, but there some issue where that overlay stalls out the whole app.

[Katherine4]

This solved my issue as well, but begs the question, "Where is the iframe coming from?"...

[Devin V_]

From what I've read, many people suspect that that iframe comes from the react-error-overlay dependency.

There appears to be some issue between the current versions of react-error-overlay and the websockets dependencies that the now-cli is using.