Next.js: These dependencies were not found in node_modules:

[serkandyck]

im using Beta.7 and 8 try but not fixed me.

• react-hot-loader/patch
• webpack-hot-middleware/client?overlay=false&reload=true
• babel-runtime/helpers/toConsumableArray
• babel-runtime/core-js/get-iterator
• babel-runtime/core-js/object/keys
• react
• react-dom
• babel-runtime/core-js/object/define-property
• react
• babel-runtime/core-js/get-iterator
• babel-runtime/core-js/object/keys
• react-hot-loader
• babel-runtime/core-js/promise
• babel-runtime/helpers/classCallCheck
• babel-runtime/helpers/classCallCheck
• babel-runtime/helpers/createClass
• babel-runtime/helpers/createClass
• babel-runtime/helpers/extends
• babel-runtime/core-js/object/get-prototype-of
• babel-runtime/helpers/possibleConstructorReturn
• babel-runtime/helpers/inherits
• babel-runtime/helpers/slicedToArray
• babel-runtime/core-js/object/entries
• glamor
• babel-runtime/core-js/promise
• babel-runtime/helpers/extends
• babel-runtime/helpers/classCallCheck
• babel-runtime/helpers/createClass
• babel-runtime/helpers/possibleConstructorReturn
• babel-runtime/helpers/inherits
• babel-runtime/core-js/object/get-prototype-of
• babel-runtime/regenerator
• babel-runtime/helpers/asyncToGenerator
• babel-runtime/core-js/set
• babel-runtime/helpers/defineProperty
• babel-runtime/core-js/object/assign

Missed Packages

Win 10
Node v6.9.2
NPM 3.10.9
still using yarn but no luck :(
yarn version v0.18.1

Try next 2.0.0.beta8

[rauchg]

Can you supply a github repo / gist with a package.json and minimal example that reproduces this?

[serkandyck]

i'm using next example project not changing any thing

this error about a npm cache maybe ?

[serkandyck]

im try fresh folder name and fresh install ssr-cache example now server started but if open browser and connect dev server return :
SyntaxError: Unexpected token m in JSON at position 0

this error
https://gist.github.com/SerkanDayicik/e867a72a171b6e1a6d1f87e5f0a654a9

[arunoda]

@SerkanDayicik if you are using yarn try yarn upgrade too.

[ryancole]

This is happening to me as well, all of a sudden. I reverted back to beta.6, etc, because I knew those worked previously but now I'm getting these errors on those versions too. Makes me think I'm doing something wrong or this issue is related to something more "global". I'm also on Windows 10.

Here's my repo. It's not prepared as a minimal example, but I do believe you should be able to clone, npm install and then npm start to see the error. Nothing platform specific, afaik.

https://github.com/ryancole/league/tree/nextjs/packages/league-client

Note: it is in the nextjs branch.

[ryancole]

I just wanted to note the actual error message that I'm receiving ...

ERROR  Failed to compile with 42 errors

These dependencies were not found in node_modules:

* ./pages/index.js?entry
* ./pages/team/detail.js?entry
* ./pages/team/index.js?entry
* C:\Users\Ryan\Projects\league\packages\league-client\node_modules\next\dist\pages\_error.js?entry
* C:\Users\Ryan\Projects\league\packages\league-client\node_modules\next\dist\pages\_error-debug.js?entry
* C:\Users\Ryan\Projects\league\packages\league-client\node_modules\next\dist\pages\_document.js?entry
* react-hot-loader/patch
* webpack-hot-middleware/client?overlay=false&reload=true
* babel-runtime/helpers/toConsumableArray
* babel-runtime/core-js/get-iterator
* babel-runtime/core-js/object/keys
* react
* react-dom
* babel-runtime/core-js/object/define-property
* babel-runtime/core-js/get-iterator
* babel-runtime/core-js/object/keys
* react
* react-hot-loader
* babel-runtime/core-js/promise
* babel-runtime/helpers/classCallCheck
* babel-runtime/helpers/classCallCheck
* babel-runtime/helpers/createClass
* babel-runtime/helpers/createClass
* babel-runtime/helpers/slicedToArray
* babel-runtime/core-js/object/entries
* glamor
* babel-runtime/helpers/extends
* babel-runtime/core-js/object/get-prototype-of
* babel-runtime/helpers/possibleConstructorReturn
* babel-runtime/helpers/inherits
* babel-runtime/core-js/promise
* babel-runtime/helpers/extends
* babel-runtime/helpers/classCallCheck
* babel-runtime/helpers/createClass
* babel-runtime/helpers/possibleConstructorReturn
* babel-runtime/helpers/inherits
* babel-runtime/core-js/object/get-prototype-of
* babel-runtime/regenerator
* babel-runtime/helpers/asyncToGenerator
* babel-runtime/core-js/set
* babel-runtime/helpers/defineProperty
* babel-runtime/core-js/object/assign

Did you forget to run npm install --save for them?

[arunoda]

One of the issue is your node_modules directory is not inside the src.
We assumed that. But that's wrong.

I'll work on a fix today.

[ryancole]

@arunoda I'm super confused, though. I've had this project structure for a few days now. Everything worked as recently as a day or two ago. I literally changed nothing, except for nuking node_modules and re-installing. Does this still jive with your assessment?

[arunoda]

@ryancole We changed something :)
I'll work on a fix.

[ryancole]

no worries! thanks for your efforts.

[nkzawa]

592 should fix the issue.

[ryancole]

@nkzawa It does appear to fix the issue, thanks! On Windows 10, this patch does indeed fix the error reported by OP, on my end.

As noted in #593, though, many of the tests are failing and npm link shows an over-all fail. Just an FYI.