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

App stuck at [wait] compiling ... using custom-express-server example #7259

Closed
novellito opened this issue May 5, 2019 · 7 comments · Fixed by #7264
Closed

App stuck at [wait] compiling ... using custom-express-server example #7259

novellito opened this issue May 5, 2019 · 7 comments · Fixed by #7264

Comments

@novellito
Copy link

Bug report

Describe the bug

When using the custom-server-express example The application seems to run fine but the console is stuck at [ wait ] compiling ...

To Reproduce

  1. Clone the repo
  2. Run:
npm install
npm run dev

Expected behavior

The console should output [ ready ] compiled successfully

Screenshots

Screen Shot 2019-05-05 at 12 42 32 PM

System information

  • OS: [macOS]

  • Version of Next.js: latest

  • Version of Express: ^4.14.0

@vincezun
Copy link

vincezun commented May 5, 2019

Me too. I thought that it is not working but when I visit my page it is actually working.
Express: ^4.16.4
OS: Windows
Next: ^8.1.0

@kandros
Copy link
Contributor

kandros commented May 26, 2019

Confirm, also using custom server via const { createServer } = require('http')
stuck at

[ wait ]  compiling ...

but navigating to the server in works

@novellito
Copy link
Author

@kandros this has been resolved here. If you update your nextjs version this issue should be fixed.

@jonnydungeons
Copy link

@novellito I am on the latest version ^8.1.0. Has this fix been promoted to the master branch or is this on in canary? If it is only in canary then do you want us to update to the canary branch?

@novellito
Copy link
Author

@J0NNYZER0 I believe this is only on the canary branch. Not too sure when it'll be moved to master but afaik the canary branch is the most up to date branch.

@asthinasthi
Copy link

I had a mysterious

import build from 'next/dist/build';

line in one of my components which caused this. May be a VSCode autocomplete issue for me

@balazsorban44
Copy link
Member

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants