Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The analyze-bundles example has a console error #6361

Closed
saltycrane opened this issue Feb 20, 2019 · 1 comment
Closed

The analyze-bundles example has a console error #6361

saltycrane opened this issue Feb 20, 2019 · 1 comment

Comments

@saltycrane
Copy link

Examples bug report

Example name

analyze-bundles

Describe the bug

After following the "Download manually" instructions, there is an error in the terminal and the page at http://localhost:3000/ displays "Internal Server Error"

To Reproduce

  1. curl https://codeload.github.com/zeit/next.js/tar.gz/canary | tar -xz --strip=2 next.js-canary/examples/analyze-bundles
  2. cd analyze-bundles
  3. npm install
  4. npm run dev
  5. See the following error:
 ERROR  Failed to compile with 1 errors                                          6:03:15 PM

 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

Expected behavior

Expect to see no errors.

System information

  • OS: macOS 10.14.2
  • Browser: Chrome 72
  • Version of Next.js: 8.0.1
  • Node: v10.15.0
  • npm: v6.8.0

Additional context

Looks to be caused by #6259

@timneutkens
Copy link
Member

Duplicate of #6240

@timneutkens timneutkens marked this as a duplicate of #6240 Feb 20, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Feb 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants