
Security News
Another Round of TEA Protocol Spam Floods npm, But It’s Not a Worm
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.
typed-i18next
Advanced tools
Type-safe translations generator for i18next.
[languageName]/**/[namespace].json.[languageName].json.const { t } = useTranslation() from react-i18next package. ExampleInstall typed-i18next package.
$ npm install typed-i18next
Latest dev build is published under canary tag.
$ npm install typed-i18next@canary
To start using the tool:
$ typed-i18next -h
When generating TypeScript types:
$ typed-i18next -i ./src/i18next/translations -o ./src/i18next/translations.d.ts
During CI, declaration file can be checked if they are up-to-date with --check flag:
$ typed-i18next -i ./src/i18next/translations -o ./src/i18next/translations.d.ts --check
$ typed-i18next -h
| CLI Flag | Type | Description | Default |
|---|---|---|---|
| -i, --input <path> | string | Location where translations are located. | |
| -o, --outputFile <file-path> | string | Location where to generate definitions file. | |
| --check [boolean] | boolean | Check if generated file up to date (useful for CI). | false |
| --logLevel <level> | "silent", "error", "warning", "info", "debug", "trace" | Console log level. | "info" |
Example translations file structure:
.
└── translations/
├── en/
│ ├── commons.json
│ ├── validation.json
│ ├── glosarry.json
│ └── pages/
│ ├── login.json
│ └── register.json
└── lt/
├── commons.json
├── validation.json
├── glosarry.json
└── pages/
├── login.json
└── register.json
react-i18nextimport { useTranslation } from "react-i18next";
import { StrictTypedTranslations } from "typed-i18next/react";
// Declaration file "translations.d.ts" that we generated with `typed-i18next` tool.
import { Translations } from "./translations";
export const useStrictTranslation = useTranslation as StrictTypedTranslations<typeof useTranslation, Translations>;
Released under the MIT license.
FAQs
Type-safe translations generator for i18next.
We found that typed-i18next demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Recent coverage mislabels the latest TEA protocol spam as a worm. Here’s what’s actually happening.

Security News
PyPI adds Trusted Publishing support for GitLab Self-Managed as adoption reaches 25% of uploads

Research
/Security News
A malicious Chrome extension posing as an Ethereum wallet steals seed phrases by encoding them into Sui transactions, enabling full wallet takeover.