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

consider /assets path updates #185

Open
estrattonbailey opened this issue Jan 19, 2022 · 1 comment
Open

consider /assets path updates #185

estrattonbailey opened this issue Jan 19, 2022 · 1 comment

Comments

@estrattonbailey
Copy link
Member

The CLI flag is assets, but defaults to /public. Those files are copied alongside static HTML files. Files like /public/style.css are then available at /style.css in the browser.

In this scenario, the dir would pry default to /assets and then be copied to /build/static/assets so browser path would be /assets/style.css.

This keeps functions, HTML, and static assets separate (might help with caching) and prevent collisions with Vercel (where a file named /public/index.js might be served as the homepage bc of their filesystem API).
@estrattonbailey
Copy link
Member Author

Also this doesn't work lol

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
@estrattonbailey