Can't find i18n folder when deploying via @zeit/Now #462

tamer-mohamed · 2019-08-17T17:19:05Z

Describe the bug

Tried to deploy examples/simple to now but failed to run.

Occurs in next-i18next version

V1.0.0

Steps to reproduce

clone examples/simple
deploy to now
502: BAD_GATEWAY

Expected behaviour

it should run successfully on now platform

Screenshots

ERROR	Uncaught Exception	{"errorType":"Error","errorMessage":"ENOENT: no such file or directory, scandir '/var/task/static/locales/en'","code":"ENOENT","stack":["Error: ENOENT: no such file or directory, scandir '/var/task/static/locales/en'","    at Object.readdirSync (fs.js:790:3)","    at getAllNamespaces (/var/task/page.js:14724:19)","    at _default (/var/task/page.js:14729:27)","    at new NextI18Next (/var/task/page.js:17983:46)","    at Object.k7Sn (/var/task/page.js:14791:18)","    at __webpack_require__ (/var/task/page.js:23:31)","    at Module.Y0NT (/var/task/page.js:9811:63)","    at __webpack_require__ (/var/task/page.js:23:31)","    at Module.f8ve (/var/task/page.js:11600:85)","    at __webpack_require__ (/var/task/page.js:23:31)"],"errno":-2,"syscall":"scandir","path":"/var/task/static/locales/en"}
END RequestId: ba58e4b2-1a15-46d6-9693-00b1206c6973
REPORT RequestId: ba58e4b2-1a15-46d6-9693-00b1206c6973

The text was updated successfully, but these errors were encountered:

isaachinman · 2019-08-17T20:10:22Z

Duplicate of #274.

DutchPrince · 2020-03-03T13:13:14Z

I've got the same problem

isaachinman · 2020-03-03T16:41:20Z

@DutchPrince I do not have knowledge about now the now platform abstracts filesystems. I would welcome any PRs. Alternatively, you can consume your localisation content via network requests with any number of i18next plugins.

DutchPrince · 2020-03-03T18:21:02Z

@DutchPrince I do not have knowledge about now the now platform abstracts filesystems. I would welcome any PRs. Alternatively, you can consume your localisation content via network requests with any number of i18next plugins.

Thanks for your response!

What does PRs mean?

isaachinman · 2020-03-03T18:37:06Z

What does PRs mean?

Pull requests. This is open source software and relies upon contributions from the community.

Chill-Studio · 2020-07-07T14:38:34Z

Excuse me guys I probably have searched for every thread that is related to this but I can't find a way to tell the server what is the path to the locales... I didn't find anything helping me in the said duplicate #274.

I am also using vercel, did anyone manage to make it work with next-i18next ?

My locales are located in public/static/locales

But when I deploy I got this path as not found

/var/task/public/static/locales/en'

I noticed that once deployed the structure on vercel has no public/

I know that "/public/static/locales" is the default i18n path, so I tried to change it to /static/locales so it will fit the vercel structure.

So I set localePath to "static/locales"

Then is does not deploy anymore and I got this as a path not found...

****/vercel/7d248d1f/static/locales/en'

I tried also the backEnd config option without success...

I am out of idea. Help :'(
Thank you guys.

isaachinman · 2020-07-07T14:41:53Z

@Chill-Studio This issue needs to be resolved by the Vercel team, and they're aware of it: vercel/next.js#13624

Chill-Studio · 2020-07-07T15:03:45Z

Wo that's a fast answer thank you !

Arg I can see there is not workaround :(

isaachinman · 2020-07-07T15:23:48Z

At the moment, the best "workaround" is to use a different serverless platform.

limebear · 2020-07-16T10:19:13Z

Is there any other platforms recommend?

isaachinman · 2020-07-16T10:32:04Z

@limebear The issue has been resolved. Vercel is probably your best option.

anialamo · 2020-10-23T23:45:13Z

Excuse me guys I probably have searched for every thread that is related to this but I can't find a way to tell the server what is the path to the locales... I didn't find anything helping me in the said duplicate #274.

I am also using vercel, did anyone manage to make it work with next-i18next ?

My locales are located in public/static/locales

But when I deploy I got this path as not found

/var/task/public/static/locales/en'

I noticed that once deployed the structure on vercel has no public/

I know that "/public/static/locales" is the default i18n path, so I tried to change it to /static/locales so it will fit the vercel structure.

So I set localePath to "static/locales"

Then is does not deploy anymore and I got this as a path not found...

****/vercel/7d248d1f/static/locales/en'

I tried also the backEnd config option without success...

I am out of idea. Help :'(
Thank you guys.

@Chill-Studio did you found how to resolve this error? Can you help me please?

isaachinman · 2020-10-25T20:27:57Z

@anialamo Check this repo. It's deployed on Vercel here. Good luck!

DutchPrince · 2020-10-26T07:13:33Z

Thanks for this!

samiulhsohan · 2021-04-23T12:05:54Z

@isaachinman I am experiencing the same issue but for dynamic routes like pages/posts/[...slug.js]. Any idea how can I solve it? Can you please also add an example for dynamic routing on the example repo?

musps · 2021-05-05T15:40:12Z

@samiulhsohan You need add the path of your locale files

// next-i18next.config.jjs
const path = require('path')

module.exports = {
  i18n: {
    defaultLocale: "en",
    locales: ["en", "fr"],
    localePath: path.resolve('./public/locales')
  },
};

samiulhsohan · 2021-05-05T16:06:31Z

@samiulhsohan You need add the path of your locale files

// next-i18next.config.jjs
const path = require('path')

module.exports = {
  i18n: {
    defaultLocale: "en",
    locales: ["en", "fr"],
    localePath: path.resolve('./public/locales')
  },
};

@musps It worked! Thanks!

i18next/next-i18next#462 (comment)

LluisPitarch · 2021-07-30T07:01:49Z

I have fixed in my case with this config:

//next-18next.config.js

const path = require('path');

module.exports = {
  i18n: {
    defaultLocale: 'en',
    locales: ['en', 'es'],
    localePath: path.resolve('./public/locales'),
    defaultNS: 'app',
    serializeConfig: false,
  },
};

developed on Vercel i still have problems on Netlify

@musps

Change is inspired by a problem I encountered after deploying my app to vercel and getting server errors for being unable to resolve the file locations for my locales. Solution was provided by @musps in [i18next#462 (comment).

nibblesnbits · 2023-05-01T11:24:23Z

@samiulhsohan You need add the path of your locale files

// next-i18next.config.jjs
const path = require('path')

module.exports = {
  i18n: {
    defaultLocale: "en",
    locales: ["en", "fr"],
    localePath: path.resolve('./public/locales')
  },
};

I think this issue is back in recent versions (I'm on 13.2.2). I get a warning:

warn  - Invalid next.config.js options detected: 
warn  -     The value at .i18n has an unexpected property, localePath, which is not in the list of allowed properties (defaultLocale, domains, localeDetection, locales).
warn  - See more info here: https://nextjs.org/docs/messages/invalid-next-config

And it still works locally, but not in Vercel.

riccardolardi · 2023-05-24T08:10:38Z

@samiulhsohan You need add the path of your locale files

// next-i18next.config.jjs
const path = require('path')

module.exports = {
  i18n: {
    defaultLocale: "en",
    locales: ["en", "fr"],
    localePath: path.resolve('./public/locales')
  },
};

I think this issue is back in recent versions (I'm on 13.2.2). I get a warning:

warn  - Invalid next.config.js options detected: 
warn  -     The value at .i18n has an unexpected property, localePath, which is not in the list of allowed properties (defaultLocale, domains, localeDetection, locales).
warn  - See more info here: https://nextjs.org/docs/messages/invalid-next-config

And it still works locally, but not in Vercel.

I think you need to move localePath into the exported module root scope:

module.exports = {
  i18n: {
    locales: ['de-CH', 'fr', 'en'],
    defaultLocale: 'de-CH',
    localeDetection: true,
  },
  localePath: path.resolve('./public/locales'),
  reloadOnPrerender: process.env.NODE_ENV === 'development',
}

Not sure where it's documented but it worked for me.

adrai · 2023-05-24T09:16:00Z

@samiulhsohan You need add the path of your locale files

// next-i18next.config.jjs
const path = require('path')

module.exports = {
  i18n: {
    defaultLocale: "en",
    locales: ["en", "fr"],
    localePath: path.resolve('./public/locales')
  },
};

I think this issue is back in recent versions (I'm on 13.2.2). I get a warning:

warn  - Invalid next.config.js options detected: 
warn  -     The value at .i18n has an unexpected property, localePath, which is not in the list of allowed properties (defaultLocale, domains, localeDetection, locales).
warn  - See more info here: https://nextjs.org/docs/messages/invalid-next-config

And it still works locally, but not in Vercel.

I think you need to move localePath into the exported module root scope:

module.exports = {
  i18n: {
    locales: ['de-CH', 'fr', 'en'],
    defaultLocale: 'de-CH',
    localeDetection: true,
  },
  localePath: path.resolve('./public/locales'),
  reloadOnPrerender: process.env.NODE_ENV === 'development',
}

Not sure where it's documented but it worked for me.

here: https://github.com/i18next/next-i18next#vercel-and-netlify

isaachinman closed this as completed Aug 17, 2019

flolu added a commit to flolu/flolu.de that referenced this issue Jun 10, 2021

fix: set i18n locale path

00d3710

i18next/next-i18next#462 (comment)

flolu added a commit to flolu/flolu.de that referenced this issue Jun 10, 2021

fix: set i18n locale path

3e73f2e

i18next/next-i18next#462 (comment)

LemonFace0309 mentioned this issue Aug 4, 2021

fix: improved readme documentation to avoid #462 possibility #1347

Closed

yoangau mentioned this issue Oct 7, 2021

i18next properties dont seem to do anything (nonExplicitSupportedLngs does not redirect to closest locale) #1412

Closed

kasperkberg mentioned this issue Mar 2, 2022

Error when deploying translations to Vercel sergiodxa/remix-i18next#47

Closed

cf-remylenoir mentioned this issue Oct 28, 2022

fix: [] locale public path contentful/template-marketing-webapp-nextjs#84

Merged

sebastien-comeau mentioned this issue Jan 18, 2023

Set next-i18next localePath config DTS-STN/passport-status#246

Merged

stefan-oconnell mentioned this issue Jan 25, 2023

Moved localePath into i18n block to match github issue suggestion DTS-STN/passport-status#272

Closed

nibblesnbits mentioned this issue May 1, 2023

import { i18n } from "next-i18next"; works on apis/functions, but not when built #2150

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Can't find i18n folder when deploying via @zeit/Now #462

Can't find i18n folder when deploying via @zeit/Now #462

tamer-mohamed commented Aug 17, 2019 •

edited

isaachinman commented Aug 17, 2019

DutchPrince commented Mar 3, 2020

isaachinman commented Mar 3, 2020

DutchPrince commented Mar 3, 2020

isaachinman commented Mar 3, 2020

Chill-Studio commented Jul 7, 2020

isaachinman commented Jul 7, 2020

Chill-Studio commented Jul 7, 2020

isaachinman commented Jul 7, 2020

limebear commented Jul 16, 2020

isaachinman commented Jul 16, 2020

anialamo commented Oct 23, 2020

isaachinman commented Oct 25, 2020

DutchPrince commented Oct 26, 2020

samiulhsohan commented Apr 23, 2021

musps commented May 5, 2021

samiulhsohan commented May 5, 2021

LluisPitarch commented Jul 30, 2021 •

edited

nibblesnbits commented May 1, 2023

riccardolardi commented May 24, 2023

adrai commented May 24, 2023

Can't find i18n folder when deploying via @zeit/Now #462

Can't find i18n folder when deploying via @zeit/Now #462

Comments

tamer-mohamed commented Aug 17, 2019 • edited

Describe the bug

Occurs in next-i18next version

Steps to reproduce

Expected behaviour

Screenshots

isaachinman commented Aug 17, 2019

DutchPrince commented Mar 3, 2020

isaachinman commented Mar 3, 2020

DutchPrince commented Mar 3, 2020

isaachinman commented Mar 3, 2020

Chill-Studio commented Jul 7, 2020

isaachinman commented Jul 7, 2020

Chill-Studio commented Jul 7, 2020

isaachinman commented Jul 7, 2020

limebear commented Jul 16, 2020

isaachinman commented Jul 16, 2020

anialamo commented Oct 23, 2020

isaachinman commented Oct 25, 2020

DutchPrince commented Oct 26, 2020

samiulhsohan commented Apr 23, 2021

musps commented May 5, 2021

samiulhsohan commented May 5, 2021

LluisPitarch commented Jul 30, 2021 • edited

nibblesnbits commented May 1, 2023

riccardolardi commented May 24, 2023

adrai commented May 24, 2023

tamer-mohamed commented Aug 17, 2019 •

edited

LluisPitarch commented Jul 30, 2021 •

edited