Shortcomings of automatically requiring theme-dependencies

[ashmaroli]

Unlike automatically requiring runtime-dependencies of a theme-gem, porting the behavior over to remote-themes have the following shortcomings when the plugin is used outside GitHub Pages (locally or virtual container):

• The remote-theme dependencies are computed separately from the current bundle context.
  • bundle install doesn't install the remote-theme dependencies.
  • bundle exec jekyll build won't be able to require gem_name unless gem_name was already available in the current bundle context.
• The remote-theme dependencies are not versioned. Therefore, even if the remote-theme's physical gemspec locks a dependency to a certain version-range, jekyll-remote-theme (via jekyll build) would instead load whatever is the latest version of the dependency installed in the user's environment.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.