Download the PHP package kasparsd/code-prettify without Composer

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

Code Prettify for WordPress

100% automatic code highlighting using the Prettify library. No shortcodes, no classnames, fully automatic and pure awesome.

What it does

The plugin applies code highlighting automatically to all <pre> tags on the page. Compatible with Gutenberg and doesn't lock you in with specific markup requirements.

Installation

Install it from your WordPress admin, or download it from WordPress.org. It works out of the box and doesn't have any configuration options.

Development

Requires Node.js 22 (see .nvmrc) and PHP 7.4+ with Composer.

There is no separate build step. Release packaging, checksums, signing and the WordPress.org SVN deploy are all handled by @wpelevator/wp-release, which reads the repo directly and selects files via .distignore. A local dry-run of the full deploy:

Release verification

Every release ZIP embeds a checksums manifest (checksums.json, in the WordPress.org plugin-checksums format) with its Ed25519 signature. The manifest pair is part of the plugin build itself, both in the GitHub release ZIP and in the package that WordPress.org serves:

The signing key public part:

To verify a release or an installed copy with @wpelevator/wp-release — the embedded manifest and its signature are found and authenticated automatically:

The ZIP itself is additionally covered by its detached .sig, in the format WordPress core's verify_file_signature() and update clients check.

Note: verification never executes any configuration shipped inside the package; the embedded manifest is read and its Ed25519 signature checked against this public key before any file comparison.

Contributing

  1. Fork and clone the repo.
  2. Create a feature branch.
  3. Make your changes and run npm run lint.
  4. Add a changeset that describes the release impact (see below).
  5. Open a pull request against master.

Changesets

Every pull request that changes the plugin needs a changeset under .changeset/, either by hand or with the interactive helper:

In a terminal it lists the packages, asks for the bump (patch, minor or major) and copies your release note into .changeset/<name>.md. For a change that should ship without a version bump (docs, tests, refactoring), use an empty changeset:

The changeset check fails PRs that are missing one. Merging to master doesn't release anything directly:

  1. The Prepare Release workflow applies the pending changesets and opens a release pull request with the version bumps and changelog entries.
  2. Review it; merging it creates the release tag, a GitHub release with the notes from the changesets, and triggers the WordPress.org deploy with the signed checksums.

Released versions and their changes are listed in releases page.

Credits

Cover photo by Yuri Samoilov

License

GPL-2.0-or-later.

All versions of code-prettify with dependencies

PHP Build Version
Package Version
No informations.
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 kasparsd/code-prettify contains the following files

Loading the files please wait ...