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

next.js/examples/with-custom-reverse-proxy has installed, npm run dev then report errors #5052

Closed
suanmei opened this issue Aug 29, 2018 · 3 comments · Fixed by #5064
Closed
Labels
good first issue Easy to fix issues, good for newcomers

Comments

@suanmei
Copy link

suanmei commented Aug 29, 2018

Bug report

Describe the bug

with-custom-reverse-proxy can't work as the folder title describes

To Reproduce

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

  1. cd with-custom-reverse-proxy
  2. run npm i
  3. run npm run dev
  4. See error Plugin 0 specified in "/Users/shiyi/myfile/next.js/examples/with-custom-reverse-proxy/node_modules/next/babel.js" provided an invalid property of "default" (While processing preset: "/Users/shiyi/myfile/next.js/examples/with-custom-reverse-proxy/node_modules/next/babel.js")

Expected behavior

custom-reverse-proxy can work as promised.

System information

  • macOS
  • Version of Next.js: 6.1.1
@timneutkens timneutkens added help wanted good first issue Easy to fix issues, good for newcomers labels Aug 29, 2018
@mohit2872
Copy link

Can you assign me this issue?

@timneutkens
Copy link
Member

There is no way to assign issues on GitHub outside of the organization/collaborators. Posting a comment here is enough for other people seeing you're on it 🙏

@mohit2872
Copy link

Kindly bear with me. I am new to this. Can you tell me the procedure in case I want to work on this?

timneutkens pushed a commit that referenced this issue Aug 30, 2018
Fixes #5052.

Example was using babel 6.
@lock lock bot locked as resolved and limited conversation to collaborators Aug 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
good first issue Easy to fix issues, good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants