Critical dependency: require function is used in a way in which dependencies cannot be statically extracted about light-bootstrap-dashboard-react

[kershnerd]

I also have these errors when running npm start. I am on Windows 10 with the node version 8.9.3 and npm version 5.6.0.

The changes you mention in the link have already been applied so nothing to do there. Any other suggestions?

When going to localhost:3000, I get a blank screen with the following warnings and errors:

Uncaught Error: Cannot find module "." at webpackMissingModule (source-map-generator.js:8) at Object.<anonymous> (source-map-generator.js:8) at Object../node_modules/source-map/lib/source-map/source-map-generator.js (source-map-generator.js:399) at __webpack_require__ (bootstrap 460f5826bb5c10e46bdc:659) at fn (bootstrap 460f5826bb5c10e46bdc:85) at Object../node_modules/source-map/lib/source-map.js (source-map.js:6) at __webpack_require__ (bootstrap 460f5826bb5c10e46bdc:659) at fn (bootstrap 460f5826bb5c10e46bdc:85) at Object../node_modules/react-error-overlay/lib/utils/getSourceMap.js (getSourceMap.js:1) at __webpack_require__ (bootstrap 460f5826bb5c10e46bdc:659) webpackHotDevClient.js:239 ./~/source-map/lib/source-map/source-map-generator.js 8:45-52 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted printWarnings @ webpackHotDevClient.js:239 webpackHotDevClient.js:239 ./~/source-map/lib/source-map/source-map-consumer.js 8:45-52 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted printWarnings @ webpackHotDevClient.js:239 webpackHotDevClient.js:239 ./~/source-map/lib/source-map/source-node.js 8:45-52 Critical dependency: require function is used in a way in which dependencies cannot be statically extracted

[kershnerd]

I was able to fix this by upgrading the react-scripts in the package.json from 1.0.10 to 1.0.17.

@guru2228 can you confirm this fixed your issue as well?

[einazare]

Hello @guru2228 .

We've done some testing and we didn't get those warnings. Can you please tell us what nodeJs and npm versions do you have, or can you make sure you have the latest npm and nodeJs versions?
From what we've found, the problem should be here . You should make those changes.
But i would recommend you install the latest nodeJs and npm, delete node_modules from your app, and install it again with npm install .

Best, Manu.