-
Notifications
You must be signed in to change notification settings - Fork 4
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
Live Preview for VS Code #5010
Comments
Request to be presented and reviewed at FR Forum on 7/10 |
Forum outcome: Request understood. To be prioritised and taken to refinement to size. |
Hi @glenn-christmas, Live preview functionality has been shipped as part of VS Code 2.5.1 release on Control Panel (release note) Cheers, Jacob |
Thanks @jacobwoffenden. Unfortunately when I try this I get a 401 error, even after logging in with GitHub credentials. I've tried this on both Chrome and Safari. |
I've just DM'd you on Slack, would be good to see what you're doing to get to that point. FWIW I've tested this with Streamlist, Express and Python's simple server and they worked. Just to double check - are you running it on port 8081 as per the guidance? Cheers, Jacob |
Sorted - @glenn-christmas was using https://marketplace.visualstudio.com/items?itemName=ms-vscode.live-server, advised to use Python's simple server python3 -m http.server 8081 |
Describe the feature request.
Hello, I was excited to see support for NodeJS added in
VS Code 2.0.0
today. However, in order to build apps, extensions likeLive Server
orLive Preview
are essential.As the AP version of VSCode is web-based, I think this is causing problems with these extensions expecting to be able to access localhost (so e.g. I'll get errors like
127.0.0.1 refused to connect.
, as presumably VSCode is trying to access e.g.http://127.0.0.1:3000/index.html
).At the moment this means app development outside of the existing R/Python approaches can't really be done. (Unless there are other extensions you'd recommend that might solve this issue - I couldn't spot anything that didn't rely on either exposing the app to a public URL (nope from a security perspective) or using localhost as above.
Describe the context.
Short term use of VS Code:
Long term use of VS Code: Exploratory work to use React frontend/Node backend to develop and deploy web apps to the cloud platform (probably more for corporate group web apps (e.g. interactive training materials) rather than anything business critical).
Value / Purpose
If this is a super time intensive task to implement, it's probably disproportionate. However, if there is a quick fix then this would be helpful.
User Types
Analysts in Systems and Monitoring Team/Analysts who develop custom CSS/JS
The text was updated successfully, but these errors were encountered: