Skip to content

Conversation

@pushpak1300
Copy link
Member

The CI was failing because the bcmath PHP extension wasn't enabled in the GitHub Actions workflow files. Laravel Cashier requires the moneyphp/money package which depends on the bcmath extension.

Changes:

  • Added bcmath extension to lint.yaml workflow
  • Added bcmath extension to test.yaml workflow

The CI was failing because the bcmath PHP extension wasn't enabled in the
GitHub Actions workflow files. Laravel Cashier requires the moneyphp/money
package which depends on the bcmath extension.

Changes:
- Added bcmath extension to lint.yaml workflow
- Added bcmath extension to test.yaml workflow
The CI tests were failing with "could not find driver" errors when trying
to connect to SQLite databases. The pdo_sqlite PHP extension is required
for Laravel's test database connection.

Changes:
- Added pdo_sqlite extension to lint.yaml workflow
- Added pdo_sqlite extension to test.yaml workflow

This fix addresses both the bcmath dependency and the SQLite PDO driver
requirements for the CI pipeline.
Added missing steps to properly set up the SQLite database for testing:
- Create database directory and file before running migrations
- Run migrations before tests to ensure database schema exists

This resolves the issue where tests were failing due to missing database
tables.
The ignore pattern used lowercase 'components' but the actual directory
is 'Components' (capital C). On case-sensitive filesystems (Linux/CI),
this caused ESLint to parse the UI component files instead of ignoring
them, resulting in parsing errors.

Fixed by updating the ignore pattern to match the actual directory name:
- resources/js/components/ui/**/* → resources/js/Components/ui/**/*

This resolves the ~400 ESLint parsing errors in the CI pipeline.
Changed import.meta.glob to use eager loading ({ eager: true }), which
bundles all Vue pages at build time and includes them in the Vite manifest.
This allows tests to properly locate page components when rendering Inertia
responses.

Without eager loading, pages are loaded dynamically at runtime and aren't
included as separate entries in the manifest, causing "Unable to locate file
in Vite manifest" errors during test execution.

Also updated phpunit.xml to ensure proper test environment configuration.
@pushpak1300 pushpak1300 closed this Nov 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants