PHPackages                             paysera/lib-maba-webpack-extension-bundle - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [DevOps &amp; Deployment](/categories/devops)
4. /
5. paysera/lib-maba-webpack-extension-bundle

ActiveLibrary[DevOps &amp; Deployment](/categories/devops)

paysera/lib-maba-webpack-extension-bundle
=========================================

Provides extensions for maba/webpack-bundle to integrate better into developer environment

0.2.1(5y ago)29.6kPHP

Since Dec 23Pushed 5y ago9 watchersCompare

[ Source](https://github.com/paysera/lib-maba-webpack-extension-bundle)[ Packagist](https://packagist.org/packages/paysera/lib-maba-webpack-extension-bundle)[ RSS](/packages/paysera-lib-maba-webpack-extension-bundle/feed)WikiDiscussions master Synced 2mo ago

READMEChangelogDependencies (1)Versions (4)Used By (0)

lib-maba-webpack-extension-bundle
=================================

[](#lib-maba-webpack-extension-bundle)

This Bundle allows developer to hook into `maba/webpack-bundle` webpack.config.js dumping process and make changes needed for developer environment.

Why?
----

[](#why)

When working with `maba/webpack-bundle` aliases, you can often end up in situation where neither IDE (PHPStorm) or Eslint gets happy when you import something like this:

```
import { StaticTextFormGroup } from '@app/js/common/components/StaticText';
import { CheckboxFieldFormGroup } from '@app/js/common/components/CheckboxField';
```

1. Eslint yells on you about `import/no-unresolved`;
2. IDE (PHPStorm) does not helps you also - no navigation to imported module (ctrl + click);

This is because you run your project from `Docker` (or any other) container, paths in `webpack.config.js` are valid only from container but not from host, so IDE (PHPStorm) fails to recognize paths in `webpack.config.js`.

Installation
------------

[](#installation)

```
composer require --dev paysera/lib-maba-webpack-extension-bundle
```

In your `AppKernel`:

```
    if (in_array($this->getEnvironment(), array('dev', 'test'))) {
        // ...
        $bundles[] = new Paysera\Bundle\MabaWebpackExtensionBundle\PayseraMabaWebpackExtensionBundle();
    }
```

Configuration
-------------

[](#configuration)

##### As this Bundle is only needed for development purposes, we suggest you to configure it only in `config_dev.yml`.

[](#as-this-bundle-is-only-needed-for-development-purposes-we-suggest-you-to-configure-it-only-in-config_devyml)

Bundle exposes these options:

```
paysera_maba_webpack_extension:
    replace_paths:
        /home/app/src: "/home/me/Projects/my-project"
    replace_items:
        webpack_config_path: true
        alias: true
        manifest_path: true
        entry: false
    replaced_webpack_config_path: "%kernel.cache_dir%/webpack.config_%kernel.environment%.js"

maba_webpack:
    aliases:
        prefix: '%' # change the prefix to something different than "@"
```

- `replace_paths` - `array` of key-value paths to replace in `webpack.config.js`.
- `replace_items` - `array` of switches where to use `replace_paths` on.
- `replaced_webpack_config_path` - `string` where to put modified `webpack.config.js`.
- change the default `maba_webpack.aliases.prefix` to something different than `@`, `#` or `!`

Recommended setup
-----------------

[](#recommended-setup)

In your `config_dev.yml`:

```
paysera_maba_webpack_extension:
    replace_paths:
        /home/app/src: "/home/me/Projects/my-project"
```

Install `eslint-import-resolver-webpack` and configure your `.eslintrc` settings with:

```
  "settings": {
    "import/resolver": {
      "webpack": {
        "config": "app/cache/dev/webpack.config_dev.js"
      }
    }
  }
```

With these lines you'll be able to get rid of `import/no-unresolved` message.

### IDE config

[](#ide-config)

Just change IDE's `webpack.config.js` to `app/cache/dev/webpack.config_dev.js`

###  Health Score

29

—

LowBetter than 60% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity21

Limited adoption so far

Community10

Small or concentrated contributor base

Maturity53

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~359 days

Total

3

Last Release

1975d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/9d385187c2b529d5c1189dfc3763972f76738d24293593ff3db876fff82321db?d=identicon)[paysera.com](/maintainers/paysera.com)

---

Top Contributors

[![vbartusevicius](https://avatars.githubusercontent.com/u/7325630?v=4)](https://github.com/vbartusevicius "vbartusevicius (3 commits)")

---

Tags

development-environmentdockerimport-no-unresolvedmaba-webpackwebpack

### Embed Badge

![Health badge](/badges/paysera-lib-maba-webpack-extension-bundle/health.svg)

```
[![Health](https://phpackages.com/badges/paysera-lib-maba-webpack-extension-bundle/health.svg)](https://phpackages.com/packages/paysera-lib-maba-webpack-extension-bundle)
```

###  Alternatives

[deployer/deployer

Deployment Tool

11.0k25.4M206](/packages/deployer-deployer)[appwrite/server-ce

End to end backend server for frontend and mobile apps.

55.3k84.2k](/packages/appwrite-server-ce)[pragmarx/health

Laravel Server &amp; App Health Monitor and Notifier

2.0k1.0M2](/packages/pragmarx-health)[felixfbecker/language-server-protocol

PHP classes for the Language Server Protocol

22476.7M6](/packages/felixfbecker-language-server-protocol)[heroku/heroku-buildpack-php

Toolkit for starting a PHP application locally, with or without foreman, using the same config for PHP and Apache2/Nginx as on Heroku

8161.3M10](/packages/heroku-heroku-buildpack-php)[tiamo/phpas2

PHPAS2 is a php-based implementation of the EDIINT AS2 standard

4674.7k](/packages/tiamo-phpas2)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
