Download the PHP package gacela-project/phpstan-extension without Composer

On this page you can find all versions of the php package gacela-project/phpstan-extension. 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?

Informations about the package phpstan-extension

Gacela PHPStan extension — abandoned

This package is abandoned. Use gacela-project/gacela instead.

Everything this extension did is built into the framework, and more. It is also incompatible with PHPStan 2: it builds errors without the identifiers PHPStan 2 requires, so it cannot load against the PHPStan version Gacela itself needs.

The rules now ship with Gacela, for PHPStan and Psalm alike, sharing one implementation so the two analysers cannot disagree about what counts as a violation. See docs/static-analysis.md.

Migrating

Replace the include:

That include turns on the pillar rules — a *Facade must extend AbstractFacade, a facade method may only delegate, a factory may not reach for a Facade, a facade interface must stay in sync — plus real return types for the pillar accessors and for getProvidedDependency(Foo::class). None of that existed here.

The module-boundary check stays opt-in, because nothing in a class name says where a boundary falls. Its two parameters are renamed:

phpstan-extension Gacela
parameters.gacela.modulesNamespace rootNamespace
parameters.gacela.excludedNamespaces sharedNamespaces

EnforceModuleBoundariesForMethodCallRule — the one rule this package had — is CrossModuleMethodCallRule there. The check now has a second half, CrossModuleViaFacadeRule, which reports the crossings a source writes by name (new, static calls, class constants). This package never covered those.

Why it moved

The rules describe Gacela's architecture and name AbstractFacade, AbstractFactory and the rest. Kept in their own package they fell behind the framework they check — which is what happened here. Shipped with it, they move in lockstep and run against Gacela's own source on every build.


All versions of phpstan-extension with dependencies

PHP Build Version
Package Version
Requires php Version >=8.0
gacela-project/gacela Version >=0.1
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 gacela-project/phpstan-extension contains the following files

Loading the files please wait ...