@webpro/next-translate-plugin/README.md

Tiny and powerful i18n plugin to translate your Next.js pages.

<h2 align="center">
    <b>Next-translate-plugin</b>
</h2>
<p align="center">
    <b>Webpack plugin</b>
</p>

<p align="center">
    (Maybe TurboPack in the future)
</p>

<p align="center">
    <img src="images/logo.svg" width="200" alt="next-translate" />
</p>

<div align="center">

[![npm version](https://badge.fury.io/js/next-translate-plugin.svg)](https://badge.fury.io/js/next-translate-plugin)
[![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat-square)](https://github.com/aralroca/next-translate-plugin/blob/main/CONTRIBUTING.md)
<a href="https://github.com/aralroca/next-translate/actions?query=workflow%3ACI" alt="Tests status">
<img src="https://github.com/aralroca/next-translate/workflows/CI/badge.svg" /></a>
<a href="https://twitter.com/intent/follow?screen_name=aralroca">
<img src="https://img.shields.io/twitter/follow/aralroca?style=social&logo=twitter"
            alt="follow on Twitter"></a>

</div>

<hr />

Two of the goals of **[next-translate](https://github.com/aralroca/next-translate)** is to be a **tiny library** (~2kb) and to have **no external dependencies**.

Since **this plugin uses TypeScript compiler** dependency, and we don't want you to have to bring extra kb into the pipeline, we have chosen to separate **next-translate** and **next-translate-plugin** with two distinct packages. 

This way you can save this as `devDependencies` instead of dependencies.

```sh
yarn add next-translate-plugin -D
```

or

```sh
npm install next-translate-plugin --save-dev
```

## Documentation

All the documentation is in Next-translate repository:

- [Next-translate GitHub repository](https://github.com/aralroca/next-translate)

## Contributors ✨

Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/docs/en/emoji-key)):

- [Contributors list is in Next-translate GitHub repository](https://github.com/aralroca/next-translate#contributors-)