react-view | Koa view engine which renders React components | Server Side Rendering library

Your webpack config doesn't handle React's JSX syntax. You need to update it with some loaders for this to work (here's a tutorial: https://www.valentinog.com/blog/babel/)

I would recommend you use create-react-app at first, which abstracts all those configurations away: https://github.com/facebook/create-react-app . It is way easier to get started with react this way and you can customise it when you're ready/if you need to.

Had the same issue. Updating the node.js fixed that for me

I finally figured out.

Initially it seems @my-company-repository/componentXPTO/node_modules/@my-company-repository/commonComponents has causing the problem looking for the react at @my-company-repository/componentXPTO/node_modules/ folder. But react don't exists there because it is a peerDependency.

So I needed to remap that through the StealJS. For that, in my package.json I added a StealJS configuration:

Ok so that was a bit of a painful lesson in html and Selenium. Anyway, I figured it out by creating a list of all the menu items and then iterating through that list and clicking on the one I wanted. At the moment, I have this:

Perhaps you need to add event.persist() before triggering handleSubmit function. For exxample:

You can directly pass the div id you want in the code below ;

As evident from the docs -

This is an Express view engine which renders React components on server. It renders static markup and does not support mounting those views on the client.

The library is just meant to render static markup and not support any client side mounting for isomorphic apps.

So basically you're not sending any js to the client ( with React and ReactDOM ) to mount the rendered component on the client and make your eventHandlers work.

To solve this, you might want to have a build pipeline ( using webpack, rollup, babel, etc) to bundle up your js files and serve them over a static server. Also for server rendering have a look at -> ReactDomServer.

You're doing server-side rendering (that's what express-react-view does), which means the lifecycle hooks of your React components will not be called.

Thus, the interval trigger on componentDidMount() won't be called. This article has a good explanation for why this is.

I believe your issue is that because you're not using Webpack or something else to transpile or bundle your code, you're not really using React. It's never loaded on the page. There is no ReactDOM.render() or anything needed to actually make use of React. You're using express-react-views which only works as a jsx view engine for Express.

From their README:

This is an Express view engine which renders React components on server. It renders static markup and does not support mounting those views on the client.

React isn't actually on the page, therefore your components lifecycle methods are never being called. Basically, it's taking what the component would look like first render, and serving that to the browser as HTML.