-
Notifications
You must be signed in to change notification settings - Fork 12k
Docs Feature Request: Serving from /dist #4290
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
Comments
I propose we also add to the docs that when you run |
`ng serve` will serve the app from memory, but it's easy to think that it just serves what's in `dist/`. This way, `dist/` is deleted on `ng serve` and users will not have a `dist/` dir where they might think the files are being served from. Partially address angular#4290
`ng serve` will serve the app from memory, but it's easy to think that it just serves what's in `dist/`. This way, `dist/` is deleted on `ng serve` and users will not have a `dist/` dir where they might think the files are being served from. Partially address #4290
`ng serve` will serve the app from memory, but it's easy to think that it just serves what's in `dist/`. This way, `dist/` is deleted on `ng serve` and users will not have a `dist/` dir where they might think the files are being served from. Partially address angular#4290
Or notify the user at the terminal when they run the command? |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Quick Ask
Please add something in the CLI docs that explains how to run the app from the
/dist
folder. Something that explains how to installlite-server
and run it on that folder as a validation or gut-check.Why? This will help skeptical folks (like me) validate that the
/dist
files will indeed run properly. The existingng serve
commands run in memory.Details
from my chat with @filipesilva ...
When I hear
build
i think that we are going to process the files and prepare them to be served. But not actually serve them. And I think there is a very clear distinction between a dev and prod build. and each of those could be either on disk or in memory. I’m not suggesting these flags, but I am using them to further explain ...then when i serve, it gets interesting …. some tools consider serve as just serving. some consider it as building and serving. For us we have …
ng serve
which builds a dev build in memory and serves it. then we haveng serve —prod
which builds a prod build in memory and serves it. Always in mem.If we wanted, we could have ...
again, im not suggesting all 8 of these. just thinking out loud
The way it actually works , we only have these …
I think those are fine … but I do see myself wanting to try a serve off disk … but we have no way of doing that with CLI. And I think it is perfectly fine to not include this in the CLI ... as long as we explain in the docs how people can run it on their own with something like http-server or lite-server.
cc // @Brocco @wardbell
The text was updated successfully, but these errors were encountered: