We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Images in resources/images go into public root directly when yarn dev or yarn build. Fonts go into fonts folder as expected.
Place a svg image in resources/images and run yarn dev. It will compile it into public/image.svg
It should compile into public/images/image.svg
I compiles into public/image.svg
No response
v10.1.7
The text was updated successfully, but these errors were encountered:
I have the same issue: all the content from the images/fonts folder and subfolder don't get compiled correctly.
Sorry, something went wrong.
thanks for the report! for now you can make this change to your bud config:
replace this:
sage/bud.config.js
Line 22 in 16d9962
with this:
.assets([ {from: app.path("@src/images"), to: app.path("@dist/images/@file")}, {from: app.path("@src/fonts"), to: app.path("@dist/fonts/@file")}, ])
Amazing! Thanks a lot for the workaround!
resolved as of newer bud (#3074)
retlehs
kellymears
No branches or pull requests
Terms
Description
What's wrong?
Images in resources/images go into public root directly when yarn dev or yarn build. Fonts go into fonts folder as expected.
Steps To Reproduce
Place a svg image in resources/images and run yarn dev. It will compile it into public/image.svg
Expected Behavior
It should compile into public/images/image.svg
Actual Behavior
I compiles into public/image.svg
Relevant Log Output
No response
Versions
v10.1.7
The text was updated successfully, but these errors were encountered: