Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Highlightjs

Highlightjs Laravel Package

components/highlightjs

A Laravel Blade component for integrating Highlight.js syntax highlighting into your views. Render highlighted code blocks with configurable languages and themes while keeping your markup clean and setup simple.

Deep Wiki
Context7

Shim repository for Highlight.js.

Frequently asked questions about Highlightjs
What is components/highlightjs used for in Laravel?
It is a Composer-distributed shim intended to deliver Highlight.js JavaScript and CSS assets into a Laravel project, not a PHP domain package. Its value is limited to apps that use Composer as an asset source or have a legacy Mix/asset pipeline. Vite/npm-first apps should normally use the npm highlight.js package directly.
How do I install components/highlightjs with Composer?
You would run composer require components/highlightjs, but the integration contract is not documented in the provided metadata. Repository, license, package type, and publish behavior are unknown, so treat installation as a spike rather than a production step. Confirm files and discovery behavior before requiring it in a branch.
Does components/highlightjs provide a Laravel Blade component or service provider?
The blurb mentions a Blade component, but the technical evaluation explicitly says auto-discovery, service provider, Blade directives, and publish paths cannot be assumed. You must inspect the package contents or run a non-production spike to verify. Do not rely on Blade integration until it is confirmed.
Which Highlight.js version and language packs are bundled?
The available metadata does not identify the upstream Highlight.js version, commit, or bundled language grammars. A shim may repackage upstream assets without a clear patching policy, so version drift and stale grammars are real risks. Pin the package version and verify asset contents before use.
Is components/highlightjs compatible with Laravel Vite?
Compatibility with Vite is unconfirmed, and the evaluation flags it as a poor fit for Vite/npm-first Laravel apps. If you use Vite, prefer npm highlight.js with a lockfile and import only the languages and styles you need. Use this shim only if Composer-based asset delivery is an established pattern.
What license applies to components/highlightjs?
The package metadata reports NOASSERTION, meaning the license is not confirmed. That is a legal and release blocker until provenance and the shim plus redistributed Highlight.js assets are reviewed. Do not ship it commercially without license clearance.
Does components/highlightjs work with a strict Content Security Policy?
Highlight.js is client-side JavaScript, so CSP behavior depends on how the assets are loaded and whether inline styles or scripts are introduced. The evaluation lists CSP incompatibility as a runtime risk, but the package details do not confirm behavior. Test under your production CSP before rollout.
Can I use npm highlight.js instead of components/highlightjs?
Yes, for most modern Laravel apps the npm highlight.js package is the preferred path, especially with Vite and a lockfile. It gives clearer versioning, smaller bundles through selected languages, and direct upstream security updates. Keep any Blade wrapper behind the same interface if you need a migration path.
Is components/highlightjs safe and maintained for production?
Maintenance signals are weak because the repository is unknown and the license is NOASSERTION. Treat it as a non-critical asset dependency with version pinning, security advisory monitoring, and a documented exit plan. Do not place it on a critical rendering path without legal and provenance review.
How should I test components/highlightjs before using it?
Run a non-production spike: require it in a branch, publish assets, and verify the actual Composer type, discovery behavior, file contents, and upstream version. Test Vite/Mix builds, CSP, SSR/hydration, browser targets, and bundle size. Then canary one non-critical view behind an abstraction before any wider use.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console
pnscripts/filament-broadquill-lite
pnscripts/laravel-sentfold-lite
vleap/mx-sdk-laravel-internal
twidpay/utils
htetmyathlaing/scout-elasticsearch-driver
artisan-toolbox/front-awesome
ls/client-assistant
users-au/laravel-client
robertmarney/lara-hierarchial-collections
simonschaufi/rule-doc-generator
emissaoja/emissaoja
blackbricksoftware/gravityforms-civicrm-form-processor
al-rahabi/fancy-crud
jinas/dhivatar-component
mltstephane/laravel-quality
bernskiold/laravel-talentlms
bernskioldmedia/laravel-form-architect