-
Notifications
You must be signed in to change notification settings - Fork 0
[BugFix] Adding missing public folder and images #82
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
Open
moda20
wants to merge
1
commit into
master
Choose a base branch
from
Improvement/name-change-update
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes
File renamed without changes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
In Vite, does using an absolute asset path like "/images/logo.png" bypass the configured base path in production builds, and is import.meta.env.BASE_URL the recommended approach for public assets?💡 Result:
No, using an absolute asset path like "/images/logo.png" (intended for public dir assets) does not bypass the configured base path in production builds when the base is absolute (e.g., "/myapp/"). However, Vite does not automatically prepend the base to hardcoded absolute paths in source code like <img src="/images/logo.png"> or '/images/logo.png' in JS strings during build—these remain as "/images/logo.png", which resolves correctly only if base is "/" or relative, but fails for subpath deploys like "/myapp/" (actual path becomes "/myapp/images/logo.png"). This is evidenced by multiple GitHub issues and Stack Overflow reports where public assets fail to load under non-root base without manual adjustment. For imported assets (e.g., import logo from '/images/logo.png'), Vite resolves and processes them to respect the base. The recommended approach for public assets when needing base support (especially dynamic or non-root base) is to use import.meta.env.BASE_URL + '/images/logo.png' for string references, or prefer importing assets directly (which get hashed and base-adjusted automatically). Official docs recommend importing over public dir unless specific needs (no hashing, no import), and explicitly note using import.meta.env.BASE_URL for dynamic URL concatenation in production builds.
Citations:
🏁 Script executed:
Repository: moda20/TypeSchedulerUI
Length of output: 144
🏁 Script executed:
Repository: moda20/TypeSchedulerUI
Length of output: 93
🏁 Script executed:
Repository: moda20/TypeSchedulerUI
Length of output: 1503
🏁 Script executed:
# Check vite config for base path configuration cat vite.config.tsRepository: moda20/TypeSchedulerUI
Length of output: 505
🏁 Script executed:
Repository: moda20/TypeSchedulerUI
Length of output: 93
🏁 Script executed:
Repository: moda20/TypeSchedulerUI
Length of output: 93
🏁 Script executed:
Repository: moda20/TypeSchedulerUI
Length of output: 409
🏁 Script executed:
Repository: moda20/TypeSchedulerUI
Length of output: 48
🏁 Script executed:
Repository: moda20/TypeSchedulerUI
Length of output: 229
🏁 Script executed:
Repository: moda20/TypeSchedulerUI
Length of output: 94
Use environment-aware asset paths for future deployment flexibility.
The hardcoded
/images/path works currently becausevite.config.tssetsbase: "/", but would break if the app is deployed under a subpath (e.g.,base: "/myapp/"). Useimport.meta.env.BASE_URLto ensure the logo loads correctly regardless of the base configuration.Suggested fix
📝 Committable suggestion
🤖 Prompt for AI Agents