search

creativetimofficial / ct-material-dashboard-pro-react

React version of Material Dashboard Pro
134 stars 25 forks source link

Unable to run dashboard react pro (react version) #157

Closed smiron closed 5 years ago

smiron commented 5 years ago

Prerequisites

Material Dashboard React Pro

Expected Behavior

Able to run the dashboard out of the box

Current Behavior

The dev server starts but it just shows a bunch of errors Example: you should not use outside a

There is an X button (top right corner). Pressing it results in an empty gray page.

This has been tried on Chrome, Edge and Safari (all latest version)

Failure Information (for bugs)

Example error message: you should not use outside a

Steps to Reproduce

I expect to be able to run the dashboard just like mentioned in the documentation

Context

Failure Logs

There are no logs

smiron commented 5 years ago

PS: also sent an email to hello@creative-tim.com

dskyberg commented 5 years ago

Experiencing the same issue with material-dashboard-pro-react-v1.5.0 and material-kit-pro-react-v1.3.0. on both Chrome Version 72.0.3626.121 and Safari Version 12.0.3 (14606.4.5) on MacOS 10.14.3 (18D109)

In a freshly unzipped folder (from CreativeTim distribution), running just 'npm i' and 'npm start'. log file attached.

localhost-1552844286100.log

forrestw92 commented 5 years ago

Same did a little digging and the issue is react-router-dom. I upgraded react-router-dom to ver. 4.4.0 and it seem to fixed the issue.

einazare commented 5 years ago

Hello there, guys,

Thank you for your interest in working with our products. Sorry for the late response, we do not work on weekends. In our package.json file we only install "react-router-dom". This package auto-installs "react-router". The problem is that is installing the latest version of "react-router", instead of the same version as "react-router-dom", and that is why you are having this error. Run the following command:

npm i -E react-router@4.3.1

And this will do the trick.

Best, Manu

smiron commented 5 years ago

Thank you Manu.

Is it possible to change the packages.json to achieve this? Doing this manually means that I need to add an extra step to my build process.

einazare commented 5 years ago

Hello again @smiron ,

I do not follow. By running that command, package.json will change.

Best, Manu

smiron commented 5 years ago

Gotcha. Thx