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

hot reload not working in v9 with global bluebird promise #8835

Closed
vugman opened this issue Sep 24, 2019 · 1 comment · Fixed by #9009
Closed

hot reload not working in v9 with global bluebird promise #8835

vugman opened this issue Sep 24, 2019 · 1 comment · Fixed by #9009
Milestone

Comments

@vugman
Copy link

vugman commented Sep 24, 2019

Bug report

Describe the bug

When using bluebird Promise as default the hot reload doesn't work in v9

The error we get - EventSource's response has a MIME type ("text/plain") that is not "text/event-stream". Aborting the connection..

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

  1. Set global.Promise = require('bluebird')
  2. Run dev server
  3. See error in browser console

Expected behavior

Hot reload should work

System information

  • Version of Next.js: 9.x

Additional context

Our projects infrastructure uses bluebird Promise and to make sure all of our projects are aligned we set global.Promise = require('bluebird') (which is a common pattern).

Once we tried to upgrade to v9 we started getting errors related to hot reloading and basically it hasn't been working since then.

The error we get is EventSource's response has a MIME type ("text/plain") that is not "text/event-stream". Aborting the connection..

If we remove that global Promise override the hot reload works again (yet, other parts of our infra. stop working..)

Since everything worked perfectly fine in the latest v8, I was wondering what changed in v9+ that might have affected this so I could try and solve this.

Thanks

@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 31, 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.

3 participants