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

bit confused with the node.js preview option #482

Closed
jasonwilliams opened this issue May 21, 2020 · 6 comments
Closed

bit confused with the node.js preview option #482

jasonwilliams opened this issue May 21, 2020 · 6 comments
Labels
*question Issue represents a question, should be posted to StackOverflow (VS Code)

Comments

@jasonwilliams
Copy link
Contributor

jasonwilliams commented May 21, 2020

Lately there's another option in my debugger menu.
node.js preview

I already have some Node launch profiles set up, do i need this option?
Im not sure what it's for or what it gives me over what i've created myself.

@connor4312
Copy link
Member

These are the new dynamic launch configurations (microsoft/vscode#95835). The goal of having these--which provide automatic configuration for things like running npm scripts, running the current file, or opening the debugger terminal--is to make it easier for people to start debugging with zero configuration; we see that a relatively small fraction of VS Code users use the editor for debugging, and we want to expand the funnel.

If you already have configurations that you added manually, you probably don't care about using the dynamic configurations 🙂

@connor4312 connor4312 added the *question Issue represents a question, should be posted to StackOverflow (VS Code) label May 21, 2020
@jasonwilliams
Copy link
Contributor Author

@connor4312 do we have a better name than node.js preview?
I didn't think this extension was preview anymore now its the default debugger. Plus the title doesn't really describe what that option does.

I know it's a bikeshed, but are there better names to use?

@connor4312
Copy link
Member

Good callout -- this month we're planning to do some name-swapping and remove the "preview" wording from the new debugger, and instead add "legacy" to the old debuggers.

@jasonwilliams
Copy link
Contributor Author

Hey @connor4312 I have a couple of questions.

this month we're planning to do some name-swapping and remove the "preview" wording from the new debugger, and instead add "legacy" to the old debuggers.

Is this still happening?

"debug.javascript.usePreview": true,

Do i still need to set this?
Im really confused whether this debugger is preview or not. The top of the readme says this still needs to be set but i assumed this debugger is now used by default? If its not the default is that planned to happen?

Whats the difference between pwa-node and just node if I have usePreview on? Aren't they the same thing?
Do we still need pwa-node? I assumed that was just there to not conflict with the old debugger.

Sometimes when I create a new launch config I have 3 node options (I usually pick pwa but i don't know what the other 2 are):

  • node
  • node2
  • pwa-node

Sorry for all the Qs I just find setting up new config not as smooth as it could be, but I'm sure this is for good reason.

@jasonwilliams
Copy link
Contributor Author

I think you may have answered some of those questions in this thread #548 (comment)

@connor4312
Copy link
Member

Some preview wording has been removed. Didn't quite fit it into september, and last month was our housekeeping month. More likely this "month" (release in early Jan); we're looking to officially deprecate the old debuggers early next year so swapping wording and setting names will come before that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
*question Issue represents a question, should be posted to StackOverflow (VS Code)
Projects
None yet
Development

No branches or pull requests

2 participants