Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / i18next/next-i18next issues and pull requests
#2316 - types: re-add `@types/hoist-non-react-statics` to dependencies
Pull Request -
State: closed - Opened by marcalexiei 14 days ago
- 3 comments
#2315 - new appWithTranslation's return type not backwards compatible
Issue -
State: closed - Opened by MadaShindeInai 14 days ago
- 8 comments
#2314 - useTranslations type mismatch - Expected 0 arguments
Issue -
State: open - Opened by emmaielle 22 days ago
- 2 comments
Labels: typescript
#2312 - Passing namespaces to `useTranslation`
Issue -
State: closed - Opened by aaimio about 1 month ago
- 2 comments
#2310 - Move @types/hoist-non-react-statics to devDependencies"
Pull Request -
State: closed - Opened by Erik-Gro 2 months ago
- 2 comments
#2309 - remove dev dependency from dependencies
Issue -
State: closed - Opened by Erik-Gro 2 months ago
- 2 comments
#2306 - feat: Rendering pages on browser when Instance i18n finished initiali…
Pull Request -
State: closed - Opened by zakudriver 3 months ago
- 9 comments
#2305 - tReady is false, and will never update to true in version 4.4.2
Issue -
State: open - Opened by qingbolove 3 months ago
- 5 comments
#2303 - The lng value is being rendered infinitely from the server component to the client component.
Issue -
State: closed - Opened by HakanSungur 4 months ago
- 11 comments
#2302 - Uncaught SyntaxError: Unexpected token
Issue -
State: closed - Opened by crackAsmiles 4 months ago
- 7 comments
#2295 - ⨯ TypeError: (0 , react__WEBPACK_IMPORTED_MODULE_0__.createContext) is not a function
Issue -
State: open - Opened by SABEYGUNA 6 months ago
- 10 comments
#2294 - Getting 'useLayoutEffect' Warning with basic nextjs setup
Issue -
State: open - Opened by SanskarDahiya 6 months ago
- 1 comment
#2292 - Error with import { initReactI18next } from "react-i18next";
Issue -
State: closed - Opened by jvictor98 6 months ago
- 1 comment
#2290 - chore(examples): add test-vitest example
Pull Request -
State: open - Opened by ImBIOS 7 months ago
- 2 comments
#2288 - @pigment-css compatibility problem
Issue -
State: closed - Opened by rkurbatov 7 months ago
- 2 comments
#2286 - Next-Intl shows messages before loading them inside google results
Issue -
State: closed - Opened by yonirosenbaum 8 months ago
- 1 comment
#2285 - locales folder names containing language and country
Issue -
State: closed - Opened by x1c0 8 months ago
- 9 comments
#2284 - add features and responsive
Pull Request -
State: closed - Opened by Pravakarcoder 8 months ago
#2281 - Type error: Type instantiation is excessively deep and possibly infinite.
Issue -
State: open - Opened by nitinmagdumvista 9 months ago
- 4 comments
Labels: typescript
#2280 - How to set the default URL language based on the language reserved by the cookie
Issue -
State: closed - Opened by JZW-6 9 months ago
- 2 comments
#2279 - Production root shows 404 while local works fine
Issue -
State: closed - Opened by LixingSun 9 months ago
- 1 comment
#2277 - Text content does not match server-rendered HTML error with app router
Issue -
State: closed - Opened by zshnb 10 months ago
- 2 comments
#2272 - `ready` always returns `true` on the server (even when ns is not in serverSideTranslations)
Issue -
State: open - Opened by arishoham 10 months ago
- 4 comments
#2271 - import_server is not defined
Issue -
State: closed - Opened by slowwriter 10 months ago
- 1 comment
#2270 - Only overwrite `ns` config if it provided
Pull Request -
State: closed - Opened by NamPNQ 11 months ago
- 8 comments
#2267 - Translations failing when page is idle for couple of hours
Issue -
State: open - Opened by PreethiVS21 11 months ago
- 13 comments
#2266 - Plugin transformers not applied server-side when App Router present
Issue -
State: closed - Opened by dmgawel 11 months ago
- 7 comments
#2265 - Hydration error when using `lang` option of `t` function
Issue -
State: closed - Opened by yamanidev 12 months ago
- 10 comments
#2264 - After setting it according to the document, "redirect(/url)" in the action file is not useful, what is the reason?
Issue -
State: open - Opened by czw333221 12 months ago
- 1 comment
#2263 - Locales are en-gh and en-us, i want my only locale region to display in the path
Issue -
State: closed - Opened by Pariola-droid 12 months ago
- 2 comments
#2261 - Translation keys flickering issue under specific language setting logic (example provided)
Issue -
State: closed - Opened by Pudge1996 about 1 year ago
- 4 comments
#2260 - doc(issue-2259): Document react state issue
Pull Request -
State: closed - Opened by pgburrack about 1 year ago
- 1 comment
#2259 - appWithTranslation is causing the React state to not consist when doing client-side page navigation.
Issue -
State: closed - Opened by pgburrack about 1 year ago
- 7 comments
#2258 - Hydration error in dynamic route.
Issue -
State: closed - Opened by JanMolcik about 1 year ago
- 6 comments
#2254 - no way to create internatiolization with Next.js 14
Issue -
State: closed - Opened by nicitaacom about 1 year ago
- 26 comments
#2253 - Changing the language the label does not update
Issue -
State: open - Opened by matteo-gobbo about 1 year ago
- 5 comments
#2249 - Allow react i18next v14
Pull Request -
State: closed - Opened by belgattitude about 1 year ago
- 2 comments
#2248 - Install error with react-i18next v14
Issue -
State: closed - Opened by belgattitude about 1 year ago
#2246 - Locale is not changing in dynamic route
Issue -
State: closed - Opened by gunsela92 about 1 year ago
- 4 comments
#2244 - Encountering Error: ENOENT: no such file or directory, scandir 'XXX' occasionally
Issue -
State: open - Opened by yuuk about 1 year ago
Labels: stale
#2243 - Config Setup not working on nextjs
Issue -
State: closed - Opened by fxmb about 1 year ago
- 3 comments
#2241 - Error when using the Trans tag with next/link: "Multiple children were passed to <Link>"
Issue -
State: closed - Opened by getsnoopy about 1 year ago
- 7 comments
#2240 - App loses translations on page transition if namespaces are split between pages
Issue -
State: closed - Opened by ckruppe about 1 year ago
- 2 comments
#2239 - Upgrading from 14.0.0 to 14.0.3 causes type errors in `next-i18next.config` file
Issue -
State: closed - Opened by mannerism about 1 year ago
- 2 comments
#2238 - Fix Spelling mistake
Pull Request -
State: closed - Opened by felixmeziere about 1 year ago
- 1 comment
#2237 - doc: add a section on fallback ssg pages in the readme
Pull Request -
State: closed - Opened by felixmeziere about 1 year ago
- 3 comments
#2236 - Bug: the entire Next app unmounts and remounts on SSG pages with fallback: true or fallback: 'blocking'.
Issue -
State: closed - Opened by felixmeziere about 1 year ago
- 9 comments
#2234 - docs: update README.md typo
Pull Request -
State: closed - Opened by diogoparente about 1 year ago
#2233 - docs: update README.md typo
Pull Request -
State: closed - Opened by diogoparente about 1 year ago
- 1 comment
#2231 - I'm using nextjs 13 (pages directory) In my dynamic pages (SSR) It can't load i18n translation and just show the kyes in server. but it's ok in development mode.
Issue -
State: closed - Opened by VahidRouzbahani over 1 year ago
- 13 comments
#2229 - When use "-" in locales, it crash. For Example: 'pt-br', 'zh-cn' will Crash, but 'ptbr', 'zhcn' is OK
Issue -
State: closed - Opened by cml98 over 1 year ago
- 2 comments
#2227 - Plural translations (with count paramater) does not match server-rendered HTML ("ua" locale)
Issue -
State: closed - Opened by nikitastryuk over 1 year ago
- 1 comment
#2226 - refactor: reuse existing instance
Pull Request -
State: closed - Opened by wjaykim over 1 year ago
- 19 comments
#2225 - Can't pass object as components prop of Trans
Issue -
State: closed - Opened by alirezahi over 1 year ago
- 1 comment
#2224 - pnpm-lock updated
Pull Request -
State: closed - Opened by nicitaacom over 1 year ago
#2222 - next-18next not comaptible with turbopack
Issue -
State: closed - Opened by FleetAdmiralJakob over 1 year ago
- 6 comments
#2221 - Migrate next-i18next to app router i18n has conflicts
Issue -
State: open - Opened by Hanggi over 1 year ago
- 12 comments
#2219 - missingKey en zod key key
Issue -
State: closed - Opened by mohrazzak over 1 year ago
- 1 comment
#2218 - useCommonProps not working with next-i18next
Issue -
State: closed - Opened by FabianDaniel00 over 1 year ago
- 2 comments
#2216 - useTranslation is not working for placeholder
Issue -
State: closed - Opened by gabrielsoaresgsm over 1 year ago
- 2 comments
Labels: stale
#2215 - support app dir
Pull Request -
State: closed - Opened by DmytroHryshyn over 1 year ago
- 1 comment
#2214 - `Internal Server Error` with [email protected]
Issue -
State: closed - Opened by peakercope over 1 year ago
- 25 comments
#2213 - Multiple translations downloads
Issue -
State: closed - Opened by williamisnotdefined over 1 year ago
- 18 comments
#2212 - An error occurs when opening the sample project using webstorm
Issue -
State: open - Opened by liangshen001 over 1 year ago
- 1 comment
Labels: stale
#2209 - Middleware cause Error : Initial locale argument was not passed into serverSideTranslations
Issue -
State: closed - Opened by geryakbarf over 1 year ago
- 3 comments
#2207 - useTranslation type inference arguments and return type doesn't take namespace into account
Issue -
State: closed - Opened by andreiciceu over 1 year ago
- 5 comments
#2206 - Add NextI18NextProvider and deprecate appWithTranslation
Issue -
State: closed - Opened by abdulqdaer-q over 1 year ago
- 9 comments
#2203 - fix: correct namespacesRequired type in serverSideTranslations
Pull Request -
State: closed - Opened by t-ondrej over 1 year ago
- 1 comment
#2202 - Middleware cause prefetch for dynamic pages fail when changing locale
Issue -
State: closed - Opened by VincentDugard over 1 year ago
- 4 comments
Labels: stale
#2201 - namespacesRequired in serverSideTranslations is not type-safe anymore
Issue -
State: closed - Opened by t-ondrej over 1 year ago
- 3 comments
Labels: typescript
#2199 - feat: can add base JSON to useTranslation hook.
Issue -
State: closed - Opened by hoseinsoleymani over 1 year ago
- 7 comments
Labels: stale
#2197 - HttpBackend Browser Failure: Error: You are passing a wrong module! Please check the object you are passing to i18next.use()
Issue -
State: closed - Opened by droegier over 1 year ago
- 2 comments
#2194 - serverSideTranslations not working with getServerSideProps on production
Issue -
State: closed - Opened by natashasq over 1 year ago
- 3 comments
#2192 - issue case: next-i18next stopped working with ISR/SSR on AWS Amplify and Vercel
Issue -
State: closed - Opened by konhi over 1 year ago
- 1 comment
#2191 - `Error: No router instance found.` while publishing to Vercel. App works normally in local `yarn dev`
Issue -
State: closed - Opened by seg-leonelsanches over 1 year ago
- 3 comments
#2190 - Redirects in loop
Issue -
State: closed - Opened by TangoPJ over 1 year ago
- 4 comments
#2189 - Doesn't fetch data on language change after serverSideTranslations been used.
Issue -
State: closed - Opened by Vahan0799 over 1 year ago
- 2 comments
#2188 - `i18next-http-backend` not working
Issue -
State: closed - Opened by necm1 over 1 year ago
- 5 comments
#2187 - The Context is reset when routing page.
Issue -
State: closed - Opened by lequangkhanh2901 over 1 year ago
- 6 comments
Labels: stale
#2186 - TypeError: labels.entries is not a function or its return value is not iterable
Issue -
State: closed - Opened by lucastonon over 1 year ago
- 2 comments
Labels: stale
#2185 - Usage example for ESM
Issue -
State: closed - Opened by nick4fake over 1 year ago
- 13 comments
Labels: help wanted, proposal
#2184 - Update link
Pull Request -
State: closed - Opened by MadaShindeInai over 1 year ago
#2182 - Can't use a LanguageSwitcher component properly
Issue -
State: closed - Opened by benetche over 1 year ago
- 1 comment
#2180 - It occurs error when returning only footer when using serverSideTranslations
Issue -
State: closed - Opened by ey920911 over 1 year ago
- 2 comments
Labels: stale
#2179 - Module not found: Can't resolve 'fs'
Issue -
State: closed - Opened by mss-souloftware over 1 year ago
- 2 comments
#2178 - Warning: Text content did not match. Server: "heroTitle1" Client: "Get your DApp"
Issue -
State: closed - Opened by ghost over 1 year ago
- 2 comments
#2176 - docs: improve changelog
Pull Request -
State: closed - Opened by belgattitude over 1 year ago
- 1 comment
#2175 - Ci typecheck examples
Pull Request -
State: closed - Opened by belgattitude over 1 year ago
#2174 - fix: refresh lock file
Pull Request -
State: closed - Opened by belgattitude over 1 year ago
#2173 - `reloadOnInterval` feature similar to `reloadOnPrerender`
Issue -
State: closed - Opened by theabdulmateen over 1 year ago
- 3 comments
#2171 - i18next.changeLanguage() changes only in-components locale, added by useTranslation
Issue -
State: closed - Opened by Edymov over 1 year ago
- 13 comments
#2170 - Support for architectural adjustments in Next v13.4.4
Issue -
State: closed - Opened by ashlyWeiting over 1 year ago
- 1 comment
#2169 - How could I change language
Issue -
State: closed - Opened by BobbleHatkjh over 1 year ago
- 1 comment
#2166 - 404 translation not work with middleware next-i18next nextjs
Issue -
State: closed - Opened by roninaruka over 1 year ago
- 9 comments
#2165 - Duplicate content on defaultLocale
Issue -
State: closed - Opened by ricoxor over 1 year ago
- 1 comment
#2164 - react-i18next:: You will need to pass in an i18next instance by using initReactI18next
Issue -
State: closed - Opened by ricoxor over 1 year ago
- 7 comments
#2163 - route locale subpath disappear when currentLanguage is defaultLanguage
Issue -
State: closed - Opened by starkbtc over 1 year ago
- 1 comment
#2161 - getNamespaces function does not includes localeStructure
Issue -
State: closed - Opened by MarcARoberge over 1 year ago
- 5 comments
Labels: stale
#2160 - Get i18n current locale in a component
Issue -
State: closed - Opened by ricoxor over 1 year ago
- 1 comment
#2158 - Cannot use appWithTranslation on app/layout.tsx
Issue -
State: closed - Opened by 2531800823 almost 2 years ago
- 1 comment