Closed lukeed closed 7 years ago
@lukeed love this!!! configuration based,
imports
is fine, if i may suggest also may call themlocal-extensions
, local-plugins
, local-tasks
or just omit the local
part
@devmondo thanks!
As mentioned in #233, I want to stay away from calling it plugins
only because it implies that you can declare public packages there too. So, there, I used localPlugins
@lukeed awesome, i noticed you call them above task
it is good too and i agree with you about your concern, i think require
too is a good candidate this goes along with Node
convensions
i noticed you call them above task it is good too
@devmondo sorry, what do you mean?
// build/custom-task-one.js
Oh, sorry. I meant custom-plugin-*.js
. This new keys is only for plugins.
Tasks can already be shared easily from within a flyfile.
exports.default = function * () {
// example "custom" task
};
exports.styles = require('./tasks/styles');
exports.scripts = require('./tasks/scripts');
man lovely!!! i cant wait for this to be released
The key is called requires
.
{
"fly": {
"requires": [
"./build/custom-plugin-one.js",
"./build/custom-plugin-two.js",
"./build/custom-plugin-three.js"
]
}
}
awesome!!!!!
@devmondo You can now access this by installing the latest beta
release.
@lukeed it is working perfectly!!!!! thank you very much
@devmondo Yippee! 🙌🏼
Pulled from #233
For the sake of reusable, private plugins:
Open to alternative names for the
imports
key.The same functionality can be achieved using
npm link
(ornpm install
andfile:./
as a dependency), but this requires that each plugin has its ownpackage.json
file.