- How do I install sokil/php-isocodes-db-i18n in a Laravel app?
- Run composer require sokil/php-isocodes sokil/php-isocodes-db-i18n. The i18n package is the localized database companion, so install it alongside the core sokil/php-isocodes library. Laravel will autoload the packages through Composer; no separate database migration is needed because the ISO data ships as package files.
- What ISO data does sokil/php-isocodes-db-i18n provide?
- It supplies translated names for ISO 3166-1 countries, ISO 3166-2 subdivisions, ISO 639-3 languages, ISO 4217 currencies, and ISO 15924 scripts. The data is the localized database companion to sokil/php-isocodes. It is not a standalone API; you query it through the core library.
- Do I need to install sokil/php-isocodes separately?
- Yes. The README installs both with composer require sokil/php-isocodes sokil/php-isocodes-db-i18n. sokil/php-isocodes-db-i18n provides the database and translations, while sokil/php-isocodes provides the lookup API. Installing only the database package will not give you the query layer.
- Does sokil/php-isocodes-db-i18n support Laravel 10, 11, and 12?
- The package is framework-agnostic and does not publish Laravel-specific version constraints. Compatibility with Laravel 10, 11, or 12 depends on the PHP version and the requirements of sokil/php-isocodes. In practice you install it via Composer and use the core library directly or bind it in a Laravel service provider.
- How often is the localized ISO database updated?
- The database is refreshed monthly on the 2nd day of every month, according to the package README. Release 4.0.29 is described as a database-only refresh to dataset v4.20.1-230-g90b9fe56. If you need more frequent updates, install only sokil/php-isocodes and manage database and i18n updates manually.
- What is the difference between sokil/php-isocodes-db-i18n and sokil/php-isocodes-db-only?
- sokil/php-isocodes-db-i18n includes localized values for country, subdivision, language, currency, and script names. sokil/php-isocodes-db-only provides the database without localized values. Use the i18n variant when you need translated display names; use the db-only variant when you only need codes and non-localized records.
- How do I get localized country names in Laravel using this package?
- Install both sokil/php-isocodes and sokil/php-isocodes-db-i18n, then use the core library's lookup methods to request localized ISO 3166-1 country names. You can wrap those calls in a Laravel service, helper, or Blade component and pass the desired locale. Cache the results if you render country lists frequently.
- Will the 4.0.29 data update break existing ISO codes in my database?
- Release 4.0.29 is a data-only refresh in the 4.0.x line, so PHP API compatibility is expected. However, the dataset moved from v4.19.0 to v4.20.1-230-g90b9fe56, and data changes can add, rename, or deprecate codes. Validate production country_code, subdivision_code, and language_code values against the new dataset and run regression tests before rollout.
- How should I cache ISO lookups when using this package in Laravel?
- Cache country, subdivision, language, currency, or script lists with a cache key that includes the package or dataset version, such as iso:countries:v4.20.1-230-g90b9fe56. That ensures a deployment of 4.0.29 invalidates stale cached lists automatically. Use Laravel's cache store and clear or version keys during deployment.
- How do I test ISO code changes after updating sokil/php-isocodes-db-i18n?
- Run your PHPUnit and Laravel integration tests for ISO lookups, validation rules, serialization, and dropdown data. Add fixtures for newly added, renamed, or deprecated ISO codes and assert that cached lookups are invalidated after deployment. Record the package version and dataset version in deployment notes so data changes are traceable.