ElMassimo / ElMassimo/jekyll-vite

Asset path issue inside post/collection

Open
#17 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Ruby
Stars
59
Forks
7
PR merge metrics
No merged PRs in 30d

Description

[troubleshooting section]: https://vite-ruby.netlify.app/guide/troubleshooting.html

- [x] I have tried upgrading by running `bundle update jekyll-vite`.
- [x] I have read the __[troubleshooting section]__ before opening an issue.

### Description 📖
While adding an img inside a post/collection, the vite_asset_path variable stops at the first item

### Reproduction 🐞

https://github.com/ghstng/jekyll-vite

Vite Ruby Info
Configuration file: /jekyll-vite/_config.yml
bin/vite present?: true
vite_ruby: 3.9.1
jekyll-vite: 3.0.4
jekyll: 4.3.4
ruby: ruby 3.3.0 (2023-12-25 revision 5124f9ac75) [x86_64-linux]
node: v18.17.1
yarn: 1.22.22

installed packages:
jekyll-vite@ /home/ghstng/jekyll-vite
├─┬ vite-plugin-ruby@5.1.1
│ └── vite@5.4.11 deduped
└── vite@5.4.11

### Screenshots 📷

Issue:
![Screenshot 2025-01-15 125601](https://github.com/user-attachments/assets/faa0b866-1d47-491c-b188-c2e91a5c9c7b)
![Screenshot 2025-01-15 125507](https://github.com/user-attachments/assets/acf162e4-a02a-4055-9367-48a193f7aaf3)

Exected:
![Screenshot 2025-01-15 143001](https://github.com/user-attachments/assets/1f68f2a7-1cfe-42b9-b4c2-db72496b4d48)

Contributor guide

Open the contributing guide

Research direction

Start with the linked reproduction repository and the troubleshooting section, then trace `vite_asset_path` when an image is used inside a post or collection. Done means the variable resolves the complete asset path instead of stopping at the first item, matching the expected result shown in the screenshots.

Written by the indexing model from the issue text.

Assessment

Tech stack
jekyll, ruby, vite
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.