# Customise Webpack Configs for Kibana (V8) Plugin development

**URL:** <https://discuss.elastic.co/t/customise-webpack-configs-for-kibana-v8-plugin-development/302542>\
**Category:** Kibana\
**Tags:** kibana-plugin-development\
**Created:** [April 16, 2022, 8:16am UTC](https://discuss.elastic.co/t/customise-webpack-configs-for-kibana-v8-plugin-development/302542 "2022-04-16T08:16:52Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![artalat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/artalat/32/104436_2.png) [@artalat](https://discuss.elastic.co/u/artalat)\
**Post date:** [April 20, 2022, 6:15pm UTC](https://discuss.elastic.co/t/customise-webpack-configs-for-kibana-v8-plugin-development/302542/4 "2022-04-20T18:15:24Z")

</div>

> [@artalat](#):
>
> Any

Thanks for the reply. The idea is to add alias to webpack configs.

Example:

```auto
// webpack.config.js
module.exports = {
  // ...the rest of your config

  resolve: {
    alias: {
      'react-native$': 'react-native-web'
    }
  }
}

```

The above example is oversimplification though. In my code, I would ideally need to have a function that takes the existing webpack config as input and returns a new one. In that case this would be my exact code:

```auto
const { resolve } = require("path");
const { withUnimodules } = require("@expo/webpack-config/addons");

module.exports = ({ config }) => {
  return withUnimodules(config, { projectRoot: resolve(__dirname, "../") });
};

```

So like I mentioned in my original post, the solution suggested by you [here](https://discuss.elastic.co/t/custom-webpack-settings-integration-with-kibana-plugin/195162/6) would be ideal. But it seems that API is now outdated?

---

_[View the full topic](https://discuss.elastic.co/t/customise-webpack-configs-for-kibana-v8-plugin-development/302542)._