Download the PHP package inlayphp/core without Composer

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

Inlay Core

Packagist PHP

Plugin, extension, asset, and render hook contracts for Inlay

The stable extension kernel shared by Inlay hosts and community plugins. It provides:

The current PHP contract version is available from Inlay\Core\Inlay::VERSION.

Install

Applications normally receive Core through inlayphp/inlay or inlayphp/panels. Install it directly when building a host or a community plugin that needs lifecycle, extension, asset, or render-hook contracts without the panel runtime.

Hosts create one context and manager, register all plugins, then boot them:

Use an explicit ExtensionManifest for publishable plugins so incompatible core versions fail before registration has side effects.

Assets use the same transport-neutral contract as @inlayphp/core:

Serialized assets contain id, source, kind, lazy, and attributes. Attribute values are strings or booleans; unsafe event-handler attributes are rejected.

Extension and render-hook ownership

Every registration records an owner. Duplicate names fail instead of silently replacing another package, and a registry checkpoint can roll back partial plugin registration when a later contribution fails. Render hooks are sorted deterministically by priority and registration order, which keeps output stable across environments.

Publishable plugins should expose a stable ID, use an ExtensionManifest with the supported Core range, perform declarations in register(), and defer container-dependent work to boot(). A host should create one PluginContext per isolation boundary, such as one Panel.

Frontend companion

@inlayphp/core mirrors contract compatibility checks, renderer registries, asset manifests, and safe URL helpers without depending on React, Vue, the DOM, or Inertia. Community packages can therefore ship one PHP plugin and separate renderer adapters while keeping the wire contract version explicit.


All versions of core with dependencies

PHP Build Version
Package Version
Requires php Version ^8.3
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 inlayphp/core contains the following files

Loading the files please wait ...