scandipwa / installer

scandipwa/installer

ScandiPWA bootstrap module

magento2-theme Compatibility: 2.4.7-2.4.9 Code Quality: Fail Tests: N/A Security: Pass OSL-3.0

ScandiPWA installer

FOSSA Status

Module is a helper to install ScandiPWA Theme.

2.0.0

Finally theme bootstrap does not rely on Magento state and scandipwa:theme:bootstrap does not require additional
setup:upgrade or initialized magento to be called.

Now copying queue is defined in Bootstrap.php directly to support non-initialized Magento states and DB-less
bootstrap and build.

Usage

  1. composer require scandipwa/installer

  2. php bin/magento scandipwa:theme:bootstrap <Vendor\name>

New theme bootstrap

Command accepts single parameter, which is treated as following format: "Vendor/theme".

Note

You can change Scandiweb/pwa in examples below to anything suitable for you, keeping the same naming structure:
Vendor/theme_name

After php bin/magento scandipwa:theme:bootstrap Scandiweb/pwa it will make next effect:

  1. Check for <magento_root>/app/design/frontend/Scandiweb/pwa - bootstrap will quite with error if directory is present to prevent unwanted overrides.
  2. Create <magento_root>/app/design/frontend/Scandiweb/pwa directory
  3. Copy necessary files to the newly created theme root.
  4. Answer y/N (No is default) to a prompt for theme.xml and registration.php generation. You might want to create
    them manually - feel free to do it!
  5. Run php bin/magento setup:upgrade.
  6. You are bootstraped!

Theme build

The theme must be built after it is bootstrap or after any changes.

  1. Go to app/design/frontend/<vendor/name>
  2. run npm ci
  3. run npm run build

Customization

In order to customize copying task - simply edit di.xml, passing array with paths.

License

FOSSA Status

No changelog yet

The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.

Versions
Version Stability QA Status Compatibility Released
4.0.1 stable Fail Magento 2.4.7-2.4.9 Details 2023-03-13 21:07:42
4.0.0 stable Not tested Not yet tested Details 2020-12-08 10:46:39
2.1.0 stable Not tested Not yet tested Details 2020-09-07 11:10:55
3.1.0 stable Not tested Not yet tested Details 2020-09-07 11:10:45
3.0.0 stable Not tested Not yet tested Details 2020-08-20 16:32:47
3.0.0-beta.1 beta Not tested Not yet tested Details 2020-06-02 15:40:02
2.0.1 stable Not tested Not yet tested Details 2020-03-05 11:13:33
2.0.0 stable Not tested Not yet tested Details 2020-02-17 12:39:47
1.6.3 stable Not tested Not yet tested Details 2020-01-24 08:34:27
1.6.1 stable Not tested Not yet tested Details 2019-10-16 09:57:51
1.6.0 stable Not tested Not yet tested Details 2019-10-16 09:41:28
1.5.0 stable Not tested Not yet tested Details 2019-09-12 08:58:58
1.4.2 stable Not tested Not yet tested Details 2019-08-07 15:04:01
1.4.1 stable Not tested Not yet tested Details 2019-08-07 11:05:27
1.4.0 stable Not tested Not yet tested Details 2019-07-29 12:38:17
1.3.2 stable Not tested Not yet tested Details 2019-06-17 10:59:08
1.3.1 stable Not tested Not yet tested Details 2019-06-14 06:32:10
1.3.0 stable Not tested Not yet tested Details 2019-05-23 10:45:45
1.2.0 stable Not tested Not yet tested Details 2019-05-10 09:56:04
1.1.1 stable Not tested Not yet tested Details 2019-04-10 07:12:44
1.0.0 stable Not tested Not yet tested Details 2019-03-08 14:39:19

Requires 2

Package Constraint
magento/framework *
magento/module-theme *

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.

Compatibility matrix (Magento × PHP)
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 Pass Pass
2.4.8 Pass Pass
2.4.9 Pass Pass

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.

Static analysis results
Tool Status Findings Summary
PHPCS Warning 14 14 warnings (ruleset: Magento2) — 10 auto-fixable with phpcbf
PHPMD Warning 4 4 rule violations (MissingImport:3, UnusedFormalParameter:1)
Cpd Pass 0
Composer validate Info 2 valid; 2 advisory notes (composer validate --strict)

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. Cell → details modal.

PHPStan results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 10 10
2.4.8 10 10
2.4.9 10 10

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

Unit tests results by Magento and PHP version
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

Integration tests results by Magento and PHP version
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.

Security results
Tool Status Findings Summary
Composer audit Pass 0
Malware scan Pass 0
License
OSL-3.0

More from scandipwa

View vendor
Make it pay

Turn 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.