left-pad VS next-i18next

It's pretty easy to find that the example I gave isn't gamed... A cursory search on GitHub can find a couple examples like dotenv [1] and npm's cli [2] both use it via an older version of nodejs/readable-stream [3].

There's also the classic left-pad debacle - https://github.com/left-pad/left-pad/issues/4

[1] - https://github.com/motdotla/dotenv/blob/master/package-lock....

when using some other modern libraries like tailwind, you have to update the Next.js version carefully or you may have some errors following the Next.js update. Nothing new in javascript world, if something is working it's not guaranteed it will last :) It is important to really read the Next.js release notes as the base configuration may change in between the releases.

It's OK, it's reddit, it happens. I will say however that unless you are deploying to a windows server on premise somewhere you are using open source. (And soon even that won't be true because eventually Windows is going to be based on Linux.) I'm not asking people to give up their weekends or anything, but IMO if you consume open source, you have an obligation to contribute back something. Even if it's just reporting a bug on some library that you use.

Funny story, on the day that they unpublished it, the package.json states the license to be "WTFPL", which allows NPM to Do What The Fuck You Want To

It had been optimized (and deprecated) since then. See https://github.com/left-pad/left-pad/blob/master/index.js

So far, we’ve been using a utility createLocalizedString to create and use the LocalizedString type. This utility is only really practical in unit tests. For real applications, we’ll want to use a translation function from react-i18next or next-i18next to do the heavy lifting. Then we just wrap the translation functions that are provided in order to use our type:

With the introduction of app directory, my previous i18n blog is not applicable anymore since next-i18next is not necessary.

Using ChatGPT Using next-i18next https://github.com/i18next/next-i18next

To get started with next-i18next, we need to install the library as a dependency in our project via a simple command (having React and Next installed is also required):

internationalization doesn't seem to work out of the box in serverless mode, you may be interested by issue_274, issue_911, issue_1311, issue_1490, issue_1552

About the stack: - Typescript - Nextjs - TailwindCSS - Styled Components - Emotion - Twin.Macro (combining Styled Components with TailwindCSS) - NextI18Next integrated (wrong translationkeys result in compilation errors) - Web3React - Ethers - Redux Toolkit + Redux Observables (with hydration example) - Ramda among others

Choose the correct package or library for React/next i18n, in this case as recommendation use i18next https://www.i18next.com/ and https://github.com/isaachinman/next-i18next for nextJS

NextJS, a well-known framework among React developers, provides multiple libraries that create a very developer-friendly environment. The most popular ones are i18Next, next-translate and, our main focus in this blog post, next-18next, a translation library that does a fantastic job helping in translation management. The following blog post will show you how to set up next-i18n in your NextJS app and manage translations with SimpleLocalize. Take a look at our demo app for the reference.

I'm trying to connect a functioning NextJS/React app that uses 'with-redux-saga' and 'with-redux' to 'next-i1iN' (https://github.com/isaachinman/next-i18next) -- but when my app boots I get the following error: