When you install a package through nimble, it performs an action called install.
If you are the author of a nimble package, you may want to have nimble run a task before or after your package is installed, for example
to git clone a dependency, echo some debug information or whatever.
To do this, you can make use of two hooks that nimble provides when using the nimscript format:
I’m playing around with luxe, building a simple depth first search-based maze generator, which I plan on turning into a full game ( btw you can try it here ).
While iterating, I had to copy-paste the content of bin/web/ to the folder linked with the project git repo, but it got old fast, and I had to find a faster way.
At first, I tried using the --output-path <path> flag in flow, that overrides the flow tree project.app.output path. The problem with this method is that flow generates two folders, web and web.build, inside your selected path, and I didn’t like it very much.
That’s when I found out about hooks, digging trough flow source code.