-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
optimizer - allow out-of-band plugins #6177
optimizer - allow out-of-band plugins #6177
Conversation
loaderPostfixes: ['-loader', ''], | ||
root: fromRoot('.'), | ||
alias: this.env.aliases, | ||
unsafeCache: this.unsafeCache, | ||
}, | ||
|
||
resolveLoader: { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how is this added function called?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's just a part of webpack config http://webpack.github.io/docs/configuration.html#resolveloader
Looks like somethinig is choking if we have a |
…portPluginsAnywhere
without this, plugins outside of the kibana code base will need to install the babel-runtime.
yep, @tsullivan, having a .babelrc file in your plugin will cause issues unless it's designed to work with babel 5. That said, we're working on removing obstacles that were being overcome with babel/gulp and ideally we will be able to drop the .babelrc files and just use kibana's babel |
LGTM |
optimizer - allow out-of-band plugins
Currently plugins need to live within the Kibana source tree in order to build properly. This shouldn't be necessary, but how to accomplish this was previously unclear. Some experimentation this morning lead to a solution that seems to work great.
Now plugins can be added by simply specifying their path via the command line: