I have the problem, that with this plugin you have to have the node infrastructure (mainly the entrypoint) inside of the jekyll source dir.
While it gives the opportunity to force jekyll watch over the possible changes, it also has the drawbacks of copying the source file into the destination directory which in my opinion can not be the desired effect.
The solution to this would be:
Let the user configure the source directory and not chdir into the source dir as this plugin is currently doing.
If the configured entry of webpack is inside of the configured source directory, then we could simply remove if afterwarts with an additional hook.
I have the problem, that with this plugin you have to have the node infrastructure (mainly the
entrypoint
) inside of the jekyll source dir.While it gives the opportunity to force jekyll watch over the possible changes, it also has the drawbacks of copying the source file into the destination directory which in my opinion can not be the desired effect.
The solution to this would be:
source
dir as this plugin is currently doing.entry
of webpack is inside of the configuredsource
directory, then we could simply remove if afterwarts with an additional hook.