In TypeScript-enabled plugins, it's a common thing to have a ./build folder with your build artifacts, which for a Gluegun plugin would include commands, extensions, and templates.
This enables Gluegun to search in a build folder if it doesn't find commands, extensions, or templates in the root of a plugin, and makes it easier to have plugins be TypeScript (or other languages) with a ./build target folder.
I considered making it configurable, but none of the options really seemed all that attractive. Since ./build is pretty common, I'm just hard-coding that.
In TypeScript-enabled plugins, it's a common thing to have a
./build
folder with your build artifacts, which for a Gluegun plugin would include commands, extensions, and templates.This enables Gluegun to search in a
build
folder if it doesn't find commands, extensions, or templates in the root of a plugin, and makes it easier to have plugins be TypeScript (or other languages) with a./build
target folder.I considered making it configurable, but none of the options really seemed all that attractive. Since
./build
is pretty common, I'm just hard-coding that.