Download the PHP package paysera/lib-maba-webpack-extension-bundle without Composer

On this page you can find all versions of the php package paysera/lib-maba-webpack-extension-bundle. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of paysera/lib-maba-webpack-extension-bundle

Informations about the package 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?

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:

  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

In your AppKernel:

Configuration

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

Bundle exposes these options:

Recommended setup

In your config_dev.yml:

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

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

IDE config

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

All versions of lib-maba-webpack-extension-bundle with dependencies

PHP Build Version
Package Version
Requires maba/webpack-bundle Version ^1.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package paysera/lib-maba-webpack-extension-bundle contains the following files

Loading the files please wait ....