Download the PHP package tyhpdef/filp-whoops without Composer

On this page you can find all versions of the php package tyhpdef/filp-whoops. 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 filp-whoops

tyhpdef/filp-whoops

Tyhp type definitions for filp/whoops 2.18.4.

This is a metapackage. Composer also installs tyhpdef/filp-whoops-impl (type files). Require this name, not tyhpdef/filp-whoops-impl.

See https://tyhplang.com.

Maintain filp/whoops? Ship the types yourself

If you are a Packagist maintainer of filp/whoops, you can take over these types.

Copy _tyhpdef/ from tyhpdef/filp-whoops-impl (Apache-2.0; keep the NOTICE). Then either:

  1. Bundle the files in filp/whoops and set extra.tyhp.package on that composer.json, plus "replace": { "tyhpdef/filp-whoops": "self.version" }, or
  2. Publish a sibling types package under your vendor, versioned with filp/whoops (same X.Y.Z). Set extra.tyhp.package there, require filp/whoops with a real constraint, "replace": { "tyhpdef/filp-whoops": "self.version" }, and set extra.tyhp.tyhpdef on filp/whoops to your sibling’s Composer name.

Ship that to Packagist first, then open an issue:

https://github.com/tyhpproject/tyhp-runtime-src/issues/new?template=tyhpdef-ownership.yml

We verify Packagist ownership and that the types parse and cover the PHP API, then stop publishing community tags for those versions. We do not transfer the tyhpdef/filp-whoops Packagist name.

Full process: TYHPDEF_OWNERSHIP.md in https://github.com/tyhpproject/tyhp-runtime-src

All versions of filp-whoops with dependencies

PHP Build Version
Package Version
Requires tyhpdef/filp-whoops-impl Version ~2.18.4.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 tyhpdef/filp-whoops contains the following files

Loading the files please wait ...