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

Exemple for Next-js is not working anymore #245

Closed
pom421 opened this issue Nov 22, 2019 · 2 comments · Fixed by vercel/next.js#10807
Closed

Exemple for Next-js is not working anymore #245

pom421 opened this issue Nov 22, 2019 · 2 comments · Fixed by vercel/next.js#10807
Assignees

Comments

@pom421
Copy link

pom421 commented Nov 22, 2019

This page is not useful anymore https://github.com/microsoft/vscode-recipes/tree/master/Next-js.

There is a dead link to the example repo: https://github.com/zeit/nextgram.

@cadamsdev
Copy link

cadamsdev commented Dec 10, 2019

Duplicate of #227, #210, #80

@vvo
Copy link

vvo commented Mar 3, 2020

Hey there, I created a PR on Next.js docs to have Next.js debugging working in either Chrome DevTools or VSCode, appreciate any feedback you have when trying it out on the PR: https://github.com/zeit/next.js/pull/10807/files?short_path=bfcc096#diff-bfcc096377efef455dd348d059704209

I choosed to only attach to the debugger from VSCode instead of trying to completely launch next from VSCode because in many occasions your Next.js application might be loaded by docker/overmind/foreman/heroku local... Let me know what you think!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants