I combined the two implementations you had previously; the 'prepArray' loads all the internal initializers first by creating those loader functions (line 173), then adds a loader function at the index '_projectInitializers' which loads the project initalizers, which gets called in order (this was the source of my previous question on async execution order).  So it has to be an 'or', since if the user does not define a custom initializer path in the config, it should default to the root 'initializer' directory, as it does in the previous version.