fix: handle root-level output path in getAssetPath #66
Conversation
When output is set to '/' or '', asset paths are calculated assuming files are 3 levels deep (src/content/docs/notes/file.mdx), but they're actually 2 levels deep (src/content/docs/file.mdx). This fix dynamically determines the path depth based on the output setting: - '' or '/': Use '../..' (2 levels) - anything else: Use '../../..' (3 levels, the default) Fixes issue where images and assets fail to load when using output: '/' with clean root-level URLs.
|
|
Someone is attempting to deploy a commit to the HiDeoo's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
Thanks for the PR 🙌 If I understand correctly, I don't think this use case should be supported by the plugin. As the plugin needs to clean previous builds to ensure that the current build only contains the latest files, using I think the best approach here would be to error in such cases (as this is not the case right now) and also maybe update the documentation to clarify that the |
|
I see. For our project a sub folder ( |
2 participants
This pull request updates the logic for determining asset paths in the
getAssetPathfunction, making asset path calculation more accurate based on the output directory depth.When output is set to '/' or '', asset paths are calculated assuming files are 3 levels deep (src/content/docs/notes/file.mdx), but they're actually 2 levels deep (src/content/docs/file.mdx).
This fix dynamically determines the path depth based on the output setting:
Fixes issue where images and assets fail to load when using output: '/' with clean root-level URLs.