msp / lightslider
msp/lightslider
Magento module wrapper for LightSlider
Magento 2 LightGallery module
This module lets you use lightSlider with Magento 2 throught requirejs.
Installation
composer require msp/lightSlider
bin/magento module:enable MSP_LightSlider
bin/magento setup:upgrade
Usage
You must include the css via layout XML, for example if you want to use the gallery in the product page add to catalog_product_view.xml:
<head>
...
<css src="MSP_LightSlider::css/lightslider.min.css"/>
...
</head>
You can init the gallery with data-mage-init:
<div id="your-slider" data-mage-init='{
"LightSlider": {
"item": 1
}
}'>
<a href="img/kitten1.jpg">
<img src="img/kitten1-thumb.jpg" />
</a>
<a href="img/kitten2.jpg">
<img src="img/kitten2-thumb.jpg" />
</a>
<a href="img/kitten3.jpg">
<img src="img/kitten3-thumb.jpg" />
</a>
</div>
or with a <script type="text/x-magento-init">:
<div id="your-gallery">
<a href="img/kitten1.jpg">
<img src="img/kitten1-thumb.jpg" />
</a>
<a href="img/kitten2.jpg">
<img src="img/kitten2-thumb.jpg" />
</a>
<a href="img/kitten3.jpg">
<img src="img/kitten3-thumb.jpg" />
</a>
</div>
<script type="text/x-magento-init">
{
"#your-slider": {
"LightSlider": {
"item": 1
}
}
}
</script>
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
Requires 3
| Package | Constraint |
|---|---|
| php | * |
| msp/common | * |
| magento/magento-composer-installer | * |
Compatibility
Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.
Code Quality
Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge. A phpcs finding can't make a module incompatible.
Static analysis
Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.
PHPStan
Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases.
Tests
Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.
Unit tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Integration tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Security
Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.
More from msp
View vendorTurn an existing module into recurring revenue.
If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.