nextjs-i18n-example
eslint-plugin-react
Our great sponsors
nextjs-i18n-example | eslint-plugin-react | |
---|---|---|
4 | 67 | |
10 | 8,810 | |
- | 0.5% | |
3.6 | 8.6 | |
about 2 years ago | 2 days ago | |
JavaScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nextjs-i18n-example
-
Translate NextJS website
We followed the steps from this article for our NextJS website translation https://localizely.com/blog/nextjs-i18n-tutorial/
-
Next.js internationalization (i18n) tutorial
More details and examples you can find in the original post.
-
How to create multi-lingual NextJS app with Github example
I just wanted to share with you a tutorial that describes how to create multi-lingual NextJS app, using popular react-intl library: https://localizely.com/blog/nextjs-i18n-tutorial/ It contains Github example that you can run and play with it.
eslint-plugin-react
-
Interesting Bugs Caught by ESLint's no-constant-binary-expression
> [1] https://github.com/jsx-eslint/eslint-plugin-react/blob/maste...
From what I remember, being able to pass children as a prop is considered a side-effect of an implementation detail, that breaks the expected abstraction. There really isn't any reason to use it, and I think there's a chance it may even confuse the virtual dom diffing?
Also this would prevent you from accidentally doing both at once:
Is it me?}>
-
Speeding up the JavaScript ecosystem – Polyfills gone rogue
I try to focus on the issues rather than individuals, but the root of the problems in the listed eslint plugin libraries points to ljharb.
If you do some simple digging into these libraries, you will find that these types of commits are quite common within them.
https://github.com/jsx-eslint/eslint-plugin-react/commit/e1d...
https://github.com/jsx-eslint/jsx-ast-utils/commit/bad51d062...
https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/commit/...
He would rather see the download count of these polyfill libraries https://github.com/ljharb/ljharb#projects-i-maintain increase, compared to assessing the health of the JavaScript ecosystem.
-
The Best ESLint Rules for React Projects
An obvious pick for React projects, but eslint-plugin-react along with their plugin:react/recommended rule set is a must. This will give you some sensible rules such as requiring a key to be specified in JSX arrays. eslint-config-airbnb is another good (if a bit loose) base rule set on top of eslint-plugin-react to start from.
-
Avoid "&&" Operator for Conditional Rendering in React
If you already have the eslint-plugin-react installed, you can enable the following rule.
-
Create React UI Lib 1.1: Ladle and ESLint
You can also add ESLint now (props to @femincan for the suggestion). It comes with recommended settings for these plugins: typescript, prettier, react, react-hooks, jsx-a11y.
- Confusion over one of the examples of the jsx-no-literals linting rule
-
What's weirdest webdev practice in your company?
Also for what it’s worth, there’s a React ESLint code rule that can enforce this behavior either way for Component props - I’m not in front of a code base atm, but I wonder if my preference for the syntax above is influenced by a popular linting preset like AirBnB which enforces this rule? https://github.com/jsx-eslint/eslint-plugin-react/blob/master/docs/rules/jsx-curly-brace-presence.md
-
Removing Default React Imports. For a Cleaner Code
The missing piece is on this page, in a small note at the end of the page: the eslint rule to disallow missing React when using JSX.
-
Ask HN: What are you predictions for 2023?
Thanks for weighing in, that's good to know. After wondering if this could be auto-refactored, I came across https://github.com/jsx-eslint/eslint-plugin-react/blob/maste..., will definitely have to give that (with `--fix`) a try in the new year and see if I can get the team on board! – desire for typescript being a compelling factor.
Personally I do like the non-destructured `props.abc` throughout component code, really helps clarify at a glance where something is coming from, whether it's locally or externally defined, etc. Code style is an endless exercise in compromises/opinions though, even _with_ tools like eslint and prettier.
-
Recommended React Hooks Convention
eslint-plugin-react react/hook-use-state
What are some alternatives?
next-translate - Next.js plugin + i18n API for Next.js 🌍 - Load page translations and use them in an easy way!
stylelint-config-prettier - Turns off all rules that are unnecessary or might conflict with prettier.
React Intl - The monorepo home to all of the FormatJS related libraries, most notably react-intl.
berry - 📦🐈 Active development trunk for Yarn ⚒
react-intl-example - React internationalization with react-intl
javascript - JavaScript Style Guide
jsLingui - 🌍 📖 A readable, automated, and optimized (3 kb) internationalization for JavaScript
prop-types - Runtime type checking for React props and similar objects
locize-lastused - Using API lastUsed using in node.js, in the browser and for deno.
razzle - ✨ Create server-rendered universal JavaScript applications with no configuration
simplelocalize-next-translate - Connect next-translate plugin for i18n with SimpleLocalize 🌍
eslint-plugin-prettier - ESLint plugin for Prettier formatting