feat: add vscode debug configurations#251
Merged
Conversation
philipj93
force-pushed
the
feature-add-debug-config
branch
from
1454972 to
39e8fc6
Compare
philipj93
changed the title
philipj93
force-pushed
the
feature-add-debug-config
branch
from
39e8fc6 to
3d914c4
Compare
kgajera
approved these changes
Mar 25, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds several VSCode debugging configurations (
.vscode/launch.json) to the default Bison template. Next.js now has recommended configs for VSCode, which can be used to debug client and server code by setting breakpoints directly in the IDE. In addition to these debug configs, two more are included for debugging production builds and database seeding.Changes
.vscode/launch.jsonfile in the default Bison template and add debug configs recommended by Next.js teamScreenshots
Checklist