Post build problems
The current post build file structure is a mess and is a chore to cleanup afterwards. Note that I am referencing the behavior of a built demo1 of html variant v8.0.36.
The following problems creep up in the file structure:
- The actual styles.bundle gets created in the theme root alongside the framework folders
- The actual plugins.bundle gets created in the folder /html
- Extra scripts of different plugins get created inside /html/demo1
- Source files get copied inside four locations in the dist folder, they always have the structure like demo1/src/*
I expect the dist folder to have everything that I need to work with the template not scour around the file structure and do trial and error with all files to make it work.
Replies (7)
Correction:
- Extra scripts of different plugins get created inside /html/demo1
They are actually CSS files.
Hi,
We will fix this issue in the next version. We are releasing it shortly. By right, you should get all generated assets in the /html/demo1/dist/assets folder
Thanks
Thanks!
I should get them under that assets folder but what i get there are the files that are already in dist, not the ones generated by the scripts.
As I have indicated, they are placed elsewhere throughout the structure. Please read my message fully.
Hi 
Thank you for your feedback. Could you please try to add --demo1 at the end of the gulp command.
For example;
gulp --demo1There is issue when the --demo1 flag is not specified. We will fix this issue sson. You should get all asset files under
/metronic_v8.0.36/html/demo1/dist/assets folder.Thanks
The separate SASS build throws an error:
[14:55:40] Using gulpfile C:\[] Work\[] Template\Metronic v8.0.36\html\tools\gulpfile.js
[14:55:40] Starting "default"...
[14:55:40] Starting "buildBundleTask"...
e TypeError: Cannot read properties of undefined (reading "on")
at proxyStream (C:\[] Work\[] Template\Metronic v8.0.36\html\tools\node_modules\duplexer\index.js:65:16)
at Array.forEach (<anonymous>)
at forEach (C:\[] Work\[] Template\Metronic v8.0.36\html\tools\node_modules\duplexer\index.js:11:20)
at duplex (C:\[] Work\[] Template\Metronic v8.0.36\html\tools\node_modules\duplexer\index.js:27:5)
at module.exports (C:\[] Work\[] Template\Metronic v8.0.36\html\tools\node_modules\stream-combiner\index.js:8:17)
at build (C:\[] Work\[] Template\Metronic v8.0.36\html\tools\node_modules\lazypipe\index.js:26:19)
at bundle (file:///C:/[]%20Work/[]%20Template/Metronic%20v8.0.36/html/tools/gulp/helpers.js:626:85)
at file:///C:/[]%20Work/[]%20Template/Metronic%20v8.0.36/html/tools/gulp/compile.js:144:9
at objectWalkRecursive (file:///C:/[]%20Work/[]%20Template/Metronic%20v8.0.36/html/tools/gulp/helpers.js:87:9)
at buildBundleTask (file:///C:/[]%20Work/[]%20Template/Metronic%20v8.0.36/html/tools/gulp/compile.js:139:3)
[14:55:40] Finished "buildBundleTask" after 42 ms
[14:55:40] Finished "default" after 46 msNot to mention there is no documentation on the Gulp instructions page, indicating what is to be expected after it completes.
