This repository has been archived by the owner on May 1, 2022. It is now read-only.
Use /public directory for static assets instead of copying from /src #65
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this fix?
Closes #64
Describe the solution
🚨 BREAKING CHANGE 🚨
Svelvet will no longer copy all assets from
./src
to./dist
. Instead, svelvet will rely on a./public
directory existing for all non-js/svelte files to live in. The dist build directory will now live inside./public/dist
instead.Directory Breakdown:
./src/
- svelvet looks for and compiles svelte files & copies js files to./public/dist/
./public/
- all your static public assets that will be served/deployed./public/dist/
- svelvet's build directoryWhy?
Copying all static files from
src
todist
for every build is just really inefficient. A staticpublic
directory makes sense here - no more copying of files and YOU get to choose which files you want public. For example, if you store your tailwind css files insidesrc
, they will not get copied topublic
BUT this allows you to compile with tailwind separately intopublic
as desired.TODO