Download the PHP package nikaia/translation-sheet without Composer

On this page you can find all versions of the php package nikaia/translation-sheet. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.


After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

All versions of translation-sheet with dependencies

Informations about the package translation-sheet

Laravel Translation Sheet

Translating Laravel languages files using a Google Spreadsheet.

Latest Version on Packagist Build Status




Laravel >= 5.1


Google Api credentials


Package configuration

In your .env file or in your published config file (config/translation_sheet.php), you need to add the following

# The service account email   

# The path to the downloaded service account credentials file

# The ID of the spreadsheet that we will be using for translation (the last portion of the spreadsheet url)

# The locales of the application (separated by comma) 


1/ Setup the spreadsheet

This need to be done only once.

2/ Prepare the sheet

To avoid some conflicts, we will first run this command to rewrite the locale languages files.

3/ Publish translation to sheet

4/ Share the spreadsheet with clients or project managers for translations.

5/ Once done, You can lock the translations on the spreadsheet (to avoid conflicts)

6/ Pull the translations

This will pull the translations from the spreadsheet, and write it the language files in your applications. You can use git diff here to make sure eveything is ok (Conflicts, errors etc ...)

6/ Unlock the translations on the spreadsheet

Open the spreadsheet in the browser

Excluding translations

Sometimes you might need to instruct the package to exclude some translations. You can do so by specifying patterns in the exclude config option. It accepts multiple patterns that target the full translation keys and that the Str::is can understand.

Extra sheets

Sometimes you may have other files that need translations. They are not related to the laravel application per se and are not stored in the resources\lang folder. Maybe you are building a web app (spa), or even a mobile app alongside the laravel app, and you need to handle their translations.

In this specific case, you can configure extra sheets to handle those translations files stored inside a specific path.

You need to run translation_sheet:setup command, if you add this config later on.


Please see CHANGELOG for more information what has changed recently.


N.B : You need a valid configuration service-account.json file to run tests.

Github action

To test your fork using github action, you need a valid service-account.json. The file is ignored in the repository to avoid exposing credentials. You need to encode your credentials file tests/fixtures/service-account.json usinggpg`

Commit the .gpg encoded file.

PS. Github action will decrypt the file just before running the tests. See the run-tests.yml file.


If you discover any security related issues, please email [email protected] instead of using the issue tracker.


Please see CONTRIBUTING for details.


Requires google/apiclient Version ^2.1
illuminate/console Version ~5.8.0|^6.0|^7.0|^8.0|^v9.0
illuminate/filesystem Version ~5.8.0|^6.0|^7.0|^8.0|^v9.0
illuminate/support Version ~5.8.0|^6.0|^7.0|^8.0|^v9.0

The package nikaia/translation-sheet contains the following files

Loading the files please wait ....