Plugins Folder Usage
Hello I purchased metronic 8 and was going through the file system of demo 1 and couldn't understand why the plugins folder exist in the path: html/demo1/src/plugins. In here there are third party plugins which all could be found on npm, so I am not sure why these are thrown here like so. Not to mention that there is already another folder called plugins in the path: html/demo1/src/js/vendors/plugins which is confusing. Can you please explain a bit about this?
Replies (3)
Hi Sean,
I am not so sure about that, I don't think that it explains it. I can't literally figure out why these js third party plugins have been thrown in here locally rather than installed though the package manager.
What makes things more confusing is that in your package.json there is literally also a dependency on fslightbox: "fslightbox": "^3.3.0-2".
Also in this plugins folder there is also toastr which I am pretty sure that I have used in another application and installed it from yarn without any issue. https://yarnpkg.com/package/toastr
Hi,
Thanks for your hint. I double-checked and confirm that we can use the latest fslightbox version from yarn. We will update this in the next update.
The reason we put it locally the previous version from yarn did not work so we had to download it from the plugin's site and use it as a local package.
The toast plugin has a known conflict with CSS class names https://getbootstrap.com/docs/5.2/components/toasts/ and if you use the toast's origin version from yarn it will throw js errors.
As a workaround, we downloaded toast and modified class names ".toast-*" to ".toastr-*" conflict.
"fonticon" is a custom icon set and "formvalidation" is a premium plugin that we purchased and included in the theme.
Regards.
Hi,
Those plugins were put in the local folder on purpose.
As I recall the NPM/Yarn package of lightbox does not have JS version. It shipped as a JS module.
​
Regards
