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

Start the localhosting explicitly #100

Open
ohritz opened this issue Dec 4, 2017 · 0 comments
Open

Start the localhosting explicitly #100

ohritz opened this issue Dec 4, 2017 · 0 comments

Comments

@ohritz
Copy link

ohritz commented Dec 4, 2017

Instead of the localhost magically starting from changing the environment.json value to true.
A more explicit method is preferable, a npm command or an action in the contextual menu in VS, preferably with its own logging ui.

Currently it is very hard to determine if it is running, and if its not see why it might not be running.
If it stops, a more direct way of starting it again would be preferable.

As I'm not prevvy to how its implemented now I dont know how valid this idea is, but personally, it would be nice to have it work in a similar way as most frontend toolings work nowadays, such as "ng serve" from the angular cli, or "npm start" scripts kicking of a webpack-dev-server or something similar.
Runing it from its own process either in a powershell/cmd/bash/cmder window would allow for instant feedback of compilation, requests and errors.

configurations in environment.json could even allow for providing paths to own certificate files.

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

No branches or pull requests

1 participant