Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

8.0.0-canary.14 bug

See original GitHub issue

Updated from 8.0.0-canary.10 with this result:

ERROR  Failed to compile with 1 errors                                                                 12:55:13 AM

 error  in ./node_modules/next/dist/client/next-dev.js

Module parse failed: Unexpected token (34:6)
You may need an appropriate loader to handle this file type.
|
|
> import('./noop');
| var _window = window,
|     assetPrefix = _window.__NEXT_DATA__.assetPrefix;

 @ multi ./node_modules/next/dist/client/next-dev

{ Error: Cannot find module '/Users/steida/dev/este/.next/build-manifest.json'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
    at Function.Module._load (internal/modules/cjs/loader.js:507:25)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:22:18)
    at Object.loadComponents (/Users/steida/dev/este/node_modules/next-server/dist/server/load-components.js:13:9)
    at DevServer.renderToHTMLWithComponents (/Users/steida/dev/este/node_modules/next-server/dist/server/next-serve
r.js:194:48)
    at DevServer.renderErrorToHTML (/Users/steida/dev/este/node_modules/next-server/dist/server/next-server.js:224:
21)
    at DevServer.renderErrorToHTML (/Users/steida/dev/este/node_modules/next/dist/server/next-dev-server.js:107:26)
    at process._tickCallback (internal/process/next_tick.js:68:7) code: 'MODULE_NOT_FOUND' }

Issue Analytics

State:
Created 5 years ago
Comments:6 (5 by maintainers)

Top GitHub Comments

6reactions

edwinwong90commented, Feb 12, 2019

For my case, I just remove node_modules and package-lock.json and run npm install again, Its works. Related #6167

1reaction

timneutkenscommented, Jan 26, 2019

@steida we’ll add acorn to Next.js’s deps to be on the safe-side of things for when we launch v8.

Top Results From Across the Web

8.0.0-canary.14 bug · Issue #6136 · vercel/next.js · GitHub

Updated from 8.0.0-canary.10 with this result: ERROR Failed to compile with 1 errors 12:55:13 AM error in ./node_modules/next/dist/client/next-dev.js Module ...

414183 - Link device fails after update on canary channel ...

After encounter this problem I am not able to turn on the device..means the system screen is getting blank,not able to view anything....

next-auth 3.2.0-canary.14 vulnerabilities | Snyk

Exploiting this vulnerability could be done via sending an invalid callbackUrl query parameter, causing an unhandled error to be thrown, leading to the...

next - npm

The React Framework. Latest version: 13.1.1, last published: 3 days ago. Start using next in your project by running `npm i next`.

Cross-site Scripting (XSS) Vulnerability in the next library

... and execute arbitrary Javascript through an error page such as a `404` or `500` error page. ... 6.0.0-canary.4-7.0.2-canary.9 ... 12.0.8-canary.14.