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.

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

Bug: Images in resources/images go into public root directly #3071

Closed
5 tasks done
SergiArias opened this issue Jun 20, 2022 · 4 comments
Closed
5 tasks done

Bug: Images in resources/images go into public root directly #3071

SergiArias opened this issue Jun 20, 2022 · 4 comments
Assignees
Milestone

Comments

@SergiArias
Copy link

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

@SergiArias SergiArias added the bug label Jun 20, 2022
@giorgiodare
Copy link

I have the same issue: all the content from the images/fonts folder and subfolder don't get compiled correctly.

@retlehs
Copy link
Sponsor Member

retlehs commented Jun 20, 2022

thanks for the report! for now you can make this change to your bud config:

replace this:

.assets('images')

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")},
    ])

@SergiArias
Copy link
Author

Amazing! Thanks a lot for the workaround!

@retlehs retlehs added this to the 10.2.0 milestone Jun 29, 2022
@retlehs
Copy link
Sponsor Member

retlehs commented Jul 12, 2022

resolved as of newer bud (#3074)

@retlehs retlehs closed this as completed Jul 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants