-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
IDE support: vscode #23
Comments
Not right now, we want to keep this repo as small as possible before Aurelia 2 Beta (no timeline). Same goes to #22. |
any chance you can help with that |
Sent a PR in. If the chrome debugger only works with webpack, make it conditional.
|
Remember you have to maintain it :-) |
I doubt it only works with webpack... I'd have to try it though to see if it's different with gulp, however... I just finally got it working! VICTORY! {
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"name": "Chrome Debugger",
"type": "chrome",
"request": "launch",
"url": "http://localhost:9000",
"webRoot": "${workspaceRoot}",
"userDataDir": "${workspaceRoot}/.chrome"
}
]
} as far as a PR on this, I'll think about it, I think I need to use vscode for like, another couple of months before I commit, I've primarily been an intellij user for the last few years, and not doing frontend dev at all. |
No worry, not urgent. |
so the Au CLI, would ask you about IDE support. Would be cool if this were added back and added recommended extensions (e.g.), the ignore #22 and more importantly a
launch.json
, I still have not gotten debugging working with the webpack/typescript setup.P.S. any chance you know why/can help with that?
The text was updated successfully, but these errors were encountered: