All side optimized Next.js translations

• next-i18next

  26 5,273 7.9 TypeScript

  The easiest way to translate your NextJs apps.

  

Let's take the example of next-i18next. While next-i18next uses i18next and react-i18next under the hood, users of next-i18next simply need to include their translation content as JSON files and don't have to worry about much else.

• i18next-locize-backend

  6 68 6.4 JavaScript

  A simple i18next backend for locize.com which can be used in Node.js, in the browser and for Deno.

  

We will use the i18next-locize-backend plugin, but only on client side.

• SurveyJS

  surveyjs.io featured

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

• i18next-chained-backend

  2 62 6.2 JavaScript

  An i18next backend to chain multiple backends (add fallbacks, caches, ...)

  

If you've configured caching for your locize version, you may not need the i18next-localstorage-backend and i18next-chained-backend plugin.

• i18next-localstorage-backend

  1 80 4.8 JavaScript

  This is a i18next cache layer to be used in the browser. It will load and cache resources from localStorage and can be used in combination with the chained backend.

  

If you've configured caching for your locize version, you may not need the i18next-localstorage-backend and i18next-chained-backend plugin.

• locize-lastused

  5 3 6.0 JavaScript

  Using API lastUsed using in node.js, in the browser and for deno.

  

Thanks to the locize-lastused plugin, you'll be able to find and filter in locize which keys are used or not used anymore.

• locize

  6 12 8.0 JavaScript

  locize InContextEditor postMessage API

  

With the help of the locize plugin, you'll be able to use your app within the locize InContext Editor.

• i18next

  61 7,413 9.2 JavaScript

  i18next: learn once - translate everywhere

  

Let's take the example of next-i18next. While next-i18next uses i18next and react-i18next under the hood, users of next-i18next simply need to include their translation content as JSON files and don't have to worry about much else.

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• vercel

  483 12,182 9.8 TypeScript

  Develop. Preview. Ship.

  

Having a backend server does not mean you are forced to run your own server. It can also be a PaaS or serverless solution, like Vercel or Netlify, etc.

• react-i18next

  71 8,942 8.8 JavaScript

  Internationalization for react done right. Using the i18next i18n ecosystem.

  

Let's take the example of next-i18next. While next-i18next uses i18next and react-i18next under the hood, users of next-i18next simply need to include their translation content as JSON files and don't have to worry about much else.

• pages-gem

  586 1,809 8.1 Ruby

  A simple Ruby Gem to bootstrap dependencies for setting up and maintaining a local Jekyll environment in sync with GitHub Pages

  

With this example, we just need a static webserver, like GitHub Pages or similar.

• Next.js

  2,047 120,804 10.0 JavaScript

  The React Framework

  

Writing Next.js code blurs the lines between client side and server side. The code is written once and depending on your needs it is then executed as SSG (static-site generation), SSR (server-side rendering) or CSR (client-side rendering), etc.

Suggest a related project