Replies: 1 comment 1 reply
-
The goal of the current integration is to improve the experience of developing a site, didn't consider themes because I personally never used themes for jekyll.
It would be interesting to have a configuration mode that makes it easier to do that, but I wouldn't want that to be the default. I'd like to hear more about the specific use cases you have in mind, without prescribing a solution. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently jekyll-vite always builds assets either in development or production modes. This means all JS packages need to be installed during build, even if the source JS hasn't changed.
Would you be open to patches to statically distribute pre-built assets? This would also enable using jekyll-vite while developing Jekyll gem-based themes.
For this to work:
publicOutputDir: "assets"
should be default for production mode. Jekyll themes load assets from anassets/
dir. Not sure yet where to configure jekyll-vite so it doesn't output files intoassets/assets/
Beta Was this translation helpful? Give feedback.
All reactions