Download the PHP package fredemmott/hack-error-suppressor without Composer
On this page you can find all versions of the php package fredemmott/hack-error-suppressor. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download fredemmott/hack-error-suppressor
More information about fredemmott/hack-error-suppressor
Files in fredemmott/hack-error-suppressor
Package hack-error-suppressor
Short Description Suppress HHVM's automatic conversion of typechecker errors to fatals.
License ISC
FAQ
Example:
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 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.
Informations about the package hack-error-suppressor
INACTIVE PROJECT
THIS PROJECT IS NO LONGER ACTIVE; it is not needed with HHVM 3.25 and later.
Hack Error Suppressor 
Unless the hhvm.hack.lang.look_for_typechecker ini setting is set to false,
by default HHVM will try to run the typechecker when loading any Hack files,
and raise a catchable runtime fatal error.
This is a PHP library that makes it convenient to temporarily disable this behavior.
When This Is Useful
HHVM's behavior is problematic when:
- HHVM can't work out where the project root is - for example, if you're trying to run Hack code from a composer plugin
- If your Hack code needs to operate on an incomplete project - for example, if you wish to write Hack code to fetch dependencies
- If your Hack code needs to operate on known-bad projects - for example, when updating generated code, the code may be inconsistent while your codegen is in process
When You Shouldn't Use This
It's probably not appropriate if any of these are true:
- it's used outside of a build/install or codegen process
- it's used when using generated code
- it's called during normal use of your software, rather than just by developers
- it's used outside of the CLI
Typechecker errors are real problems with code, and mean that things are broken; ignoring enforcement is only a good idea if you are expecting your code to be running on a temporarily-broken codebase, and your code fixes it.
Installation
Usage
You must enable error suppression before any Hack code is loaded.
You can explicitly enable and disable the suppression:
You can also enable the suppression with a scope:
Using Outside Of The CLI
This is disallowed by default; if you're absolutely certain you need to do this (keeping in mind that typechecker errors are real problems with your code, not just lint) you can disable the check:
