i18next-node-firestore-backend

v2.0.8

Use i18next with Google Firestore as the backend for storing translation data For more information about how to use this package see README

Latest version published 3 months ago

License: MIT

NPM

GitHub

Package Health Score

60 / 100

security
No known security issues
popularity
Limited
maintenance
Sustainable
community
Limited

Explore Similar Packages

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions

Version				Vulnerabilities	License Risk
2.0.8	\|	08/2024	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.0.7	\|	08/2024		0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.0.0	\|	11/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.4.0	\|	10/2021		0 C 0 H 0 M 0 L	0 H 0 M 0 L
0.2.3	\|	03/2021		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Limited

Weekly Downloads (45)

GitHub Stars: 4
Forks: 3
Contributors: 1

Direct Usage Popularity

The npm package i18next-node-firestore-backend receives a total of 45 downloads a week. As such, we scored i18next-node-firestore-backend popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package i18next-node-firestore-backend, we found that it has been starred 4 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Limited

Readme.md: Yes
Contributing.md: No
Code of Conduct: No
Contributors: 1
Funding: No

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like i18next-node-firestore-backend is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Sustainable

Commit Frequency

Open Issues: 0
Open PR: 0
Last Release: 3 months ago
Last Commit: 3 months ago

Further analysis of the maintenance status of i18next-node-firestore-backend based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Sustainable.

We found that i18next-node-firestore-backend demonstrates a positive version release cadence with at least one new version released in the past 3 months.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: >=10

Age: 4 years
Dependencies: 2 Direct
Versions: 15
Install Size: 93.7 kB
Dist-tags: 1
# of Files: 40
Maintainers: 1
TS Typings: No

i18next-node-firestore-backend has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Readme

i18next-node-firestore-backend

A plugin for i18next that supports fetching translations from a Google Cloud Firestore database. This plugin is designed to work with both the Firebase Client SDK and the Firebase Admin SDK.

Why this plugin?

i18next is a fantastic JavaScript module for internationalization -- translations of text and other values. It supports a wide variety of backends for storing translations.

Using the i18next-node-firestore-backend plugin, you have the ability to add and update translation values for your application in real-time. No need to re-deploy your application to update translations. Simply update the values in your Firestore Database and your application can fetch the new values. This plugin can be used in any JS application, including modern web systems such as React, Angular, Vue, etc. and backend/server systems such as NodeJS, ExpressJS, NestJS, etc.

Firebase SDK Versions

This plugin uses either the Firebase Client SDK API or the Firebase Admin SDK API. Version 2.0.0 and above support both the "modular" and the "namespaced" API sets.

Getting Started

See the example applications. There are two client SDK examples: a CLI written in JavaScript, and a ReactJS/Vite application. There is also an admin SDK example: a CLI app. See their respective README files for details as to how to get them running.

Acknowledgements

This project began as a copy of i18next-node-mongodb-backend (https://github.com/lamualfa/i18next-node-mongo-backend). Many thanks for your contributions!

Publishing NPM

Following the instructions from this page, we did:

make sure local repo is clean: git status
do a build: npm run build
add files and commit build output: git commit -am "dist files updated by build"
update the version in the packages & CHANGELOG.md: npm run release-bump:patch (or 'minor' or 'major')
push to your remote: git push
push tags too: npm run release:tag-push
test a publish of the NPM: npm run publish-dry-run and review output
publish the NPM: npm run publish-publish

i18next-node-firestore-backend dependencies

firebase i18next

i18next-node-firestore-backend development dependencies

codecov eslint eslint-config-airbnb-base eslint-config-prettier eslint-plugin-import eslint-plugin-jest eslint-plugin-prettier jest prettier standard-version typescript

FAQs

What is i18next-node-firestore-backend?

Use i18next with Google Firestore as the backend for storing translation data. Visit Snyk Advisor to see a full health score report for i18next-node-firestore-backend, including popularity, security, maintenance & community analysis.

Is i18next-node-firestore-backend popular?

The npm package i18next-node-firestore-backend receives a total of 45 weekly downloads. As such, i18next-node-firestore-backend popularity was classified as limited. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is i18next-node-firestore-backend well maintained?

We found indications that i18next-node-firestore-backend maintenance is sustainable demonstrating some project activity. We saw a total of 1 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is i18next-node-firestore-backend safe to use?

The npm package i18next-node-firestore-backend was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 15 November-2024, at 02:36 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (45)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Readme

i18next-node-firestore-backend

Why this plugin?

Firebase SDK Versions

Getting Started

Acknowledgements

Publishing NPM

i18next-node-firestore-backend dependencies

i18next-node-firestore-backend development dependencies

FAQs

What is i18next-node-firestore-backend?

Is i18next-node-firestore-backend popular?

Is i18next-node-firestore-backend well maintained?

Is i18next-node-firestore-backend safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues