You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issues of this repository and believe that this is not a duplicate.
Expected Behavior
The project start normally after running npm run dev (for development) or npm run build (for production)
Current Behavior
Log after running npm run dev
> [email protected] dev C:\Users\Tony\Desktop\material-ui\examples\nextjs
> next
Error: Cannot find module 'webpack'
at Function.Module._resolveFilename (module.js:538:15)
at Function.Module._load (module.js:468:25)
at Module.require (module.js:587:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (C:\Users\Tony\Desktop\material-ui\next.config.js:1:17)
at Module._compile (module.js:643:30)
at Object.Module._extensions..js (module.js:654:10)
at Module.load (module.js:556:32)
at tryModuleLoad (module.js:499:12)
at Function.Module._load (module.js:491:3)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] dev: `next`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Tony\AppData\Roaming\npm-cache\_logs\2018-02-25T03_13_50_893Z-debug.log
Log after npm run build
> [email protected] build C:\Users\Tony\Desktop\material-ui\examples\nextjs
> next build
{ Error: Cannot find module 'webpack'
at Function.Module._resolveFilename (module.js:538:15)
at Function.Module._load (module.js:468:25)
at Module.require (module.js:587:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (C:\Users\Tony\Desktop\material-ui\next.config.js:1:79)
at Module._compile (module.js:643:30)
at Object.Module._extensions..js (module.js:654:10)
at Module.load (module.js:556:32)
at tryModuleLoad (module.js:499:12)
at Function.Module._load (module.js:491:3)
at Module.require (module.js:587:17)
at require (internal/module.js:11:18)
at loadConfig (C:\Users\Tony\Desktop\material-ui\examples\nextjs\node_modules\next\dist\server\c
onfig.js:59:28)
at getConfig (C:\Users\Tony\Desktop\material-ui\examples\nextjs\node_modules\next\dist\server\co
nfig.js:42:20)
at _callee$ (C:\Users\Tony\Desktop\material-ui\examples\nextjs\node_modules\next\dist\server\bui
ld\index.js:118:43)
at tryCatch (C:\Users\Tony\Desktop\material-ui\examples\nextjs\node_modules\regenerator-runtime\
runtime.js:62:40) code: 'MODULE_NOT_FOUND' }
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] build: `next build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Tony\AppData\Roaming\npm-cache\_logs\2018-02-25T03_14_52_473Z-debug.log
Steps to Reproduce (for bugs)
Firstly, cd examples/nextjs && npm install
Then, npm run dev or npm run build to see the bugs in the console.
Context
I am trying to integrate Material-UI with NextJS server for Universal Ap. After clone the example, I can not start running the project as expected.
My Environment
Tech
Version
Material-UI
1.0.0-beta.34
React
16.2.0
React DOM
16.2.0
jss
9.8.0
react-jss
8.3.3
node
8.9.4
npm
5.6.0
OS
windows 10
The text was updated successfully, but these errors were encountered:
Can not start nextjs example server.
Expected Behavior
The project start normally after running
npm run dev
(for development) ornpm run build
(for production)Current Behavior
Log after running
npm run dev
Log after
npm run build
Steps to Reproduce (for bugs)
cd examples/nextjs && npm install
npm run dev
ornpm run build
to see the bugs in the console.Context
I am trying to integrate Material-UI with NextJS server for Universal Ap. After clone the example, I can not start running the project as expected.
My Environment
The text was updated successfully, but these errors were encountered: