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.

Sign up for GitHub

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

Jump to bottom

Why using serve-static over useStaticAssets() for SPA? #340

Closed
ghost opened this issue Oct 8, 2020 · 1 comment
Closed

Why using serve-static over useStaticAssets() for SPA? #340

ghost opened this issue Oct 8, 2020 · 1 comment

Comments

@ghost
Copy link

ghost commented Oct 8, 2020

What are the benefits of serve-static?
@kamilmysliwiec
Copy link
Member

This package is intended to minimize & simplify the boilerplate code needed for serving SPA from Nest. However, it doesn't ship with any additional features and isn't required. Using useStaticAssets() is completely fine and provides more control & gives more flexibility but at the same time, requires more configuration & understanding of express/fastify (depending on what you use).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kamilmysliwiec