My plugin:dev build takes about a minute, but my prod build takes two hours (edit: make that 3.5 hours and I have a crazy 16 core Threadripper with 128GB of RAM). What does it actually do? Why do I care about a prod build - could I just use my dev build all the time? I’ve invested a day trying to speed it up and think it might be short of memory but no amount of max-old-space seems to help.
Some more debug info that might help: I have 3 panel plugins and a data source plugin packaged in an app plugin. They are all tiny but have a dependency on a large 3D library I am using which is almost certainly the culprit. All my code and the library are TypeScript and I’m using the Terser Webpack plugin.
Alternatively suggestions on a node command that would replace the grafana-toolkit would also help as I don’t seem to be able to tweak grafana-toolkit, but I would like to know if I care about a prod build before sinking in more time.
How did you get the terser plugin into the webpack config?
I also created a monorepo (nx) to handle multiple panels, datasources, and shared libraries.
grafana was fighting me all the way through, but I eventually got it to work.
I had to look a bit into how grafana handles its webpack configs when my shared libraries would not work (for some reason it seems to ignore/override the “paths” mapping inside the tsconfig)
Unless I am mistaken, there is no webpack config as such, but the grafana/toolkit has a script that creates it at runtime. It also looks like there is some more custom logic in there that elimates code from the resulting bundle (like imports grafana dependencies which I guess the grafana runtime itself will be providing). This was also probably the cause why I had so many issues getting it to work with storybook and creating meaningful unit tests with jest (and the AMD format of the resulting bundle also did not help).
But if anyone knows more about the subject (or can point me to any documentation), I am all ears.