this PR allows to customize module paths. So instead of creating modules always in /client/modules
you can specify other paths like /import/modules which helps to leaverage lazy loading in meteor 1.5 and also to overcome restrictions on the client folder beeing not available on server
Because module creation happens also when a new mantra project is beeing created,
you can now specify an initial configuration file:
~/.defaultmantra.yaml content:
modulesPath: imports/modules
storybook: true
# and other configs...
released as 0.5.1
fixes https://github.com/mantrajs/mantra-cli/issues/117
this PR allows to customize module paths. So instead of creating modules always in /client/modules you can specify other paths like /import/modules which helps to leaverage lazy loading in meteor 1.5 and also to overcome restrictions on the client folder beeing not available on server
Because module creation happens also when a new mantra project is beeing created, you can now specify an initial configuration file:
~/.defaultmantra.yaml content:
mantra create myapp --config ~/.defaultmantra.yaml
this will create the new app with this custom configuration which will be copied into the newly created app.
I has now working tests, but its not yet tested in battle. I will release a beta version as soon it is testable