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

Files imported from a "public/" path should not be emitted elsewhere #110

Closed
cezaraugusto opened this issue Jun 21, 2024 · 1 comment
Closed

Files imported from a "public/" path should not be emitted elsewhere #110

cezaraugusto opened this issue Jun 21, 2024 · 1 comment
Assignees
@cezaraugusto
Labels
not actionable

Comments

@cezaraugusto
Copy link
Member

Right now if you import myImage from './public/path/my-image' the output path will be both '/public/path/my-image' and /assets/my-image, which is wrong.
@cezaraugusto cezaraugusto added the bug Something isn't working label Jun 21, 2024
@cezaraugusto cezaraugusto self-assigned this Sep 11, 2024
@cezaraugusto cezaraugusto added not actionable and removed bug Something isn't working labels Sep 20, 2024
@cezaraugusto
Copy link
Member Author

Decied not to do anything about it. Users are guided on how public/ works via documentation and if they want to import assets from there then they should. Extension.js should not control users behavior but rather expose when a possible bug might happen, which is not the case

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cezaraugusto cezaraugusto

Labels
not actionable
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cezaraugusto