npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@hitachivantara/app-shell-i18next

v0.2.1

Published

AppShell i18next integration

Readme

AppShell i18next integration

Optional library for apps that use the i18next library and that also implement the conventional locales resource bundles layout.

Overview

This package provides an opinionated integration between i18next and React. It is intended for applications that need to:

  • create i18n instances with sensible defaults;
  • initialize those instances from React components with predictable loading state; and
  • load translation bundles from HTTP-served locale assets.

Error handling

i18next does not provide a reliable public API to distinguish fatal initialization errors from partial load failures (where fallback resources are still usable). Therefore, useI18n does not propagate init errors.

Load failures degrade gracefully:

  • If a fallback language has resources, t() returns the fallback value.
  • If no resources are available at all, t() returns raw keys.

Applications that need stricter guarantees should implement health checks outside of the i18n layer.

[!IMPORTANT] This package is designed to be bundled with its consumers. Additionally, applications using @hitachivantara/app-shell-i18next should declare a direct dependency on i18next.

Included API

The public API exposed by this package is intentionally small:

| Export | Kind | Summary | Detailed documentation | | ------------------------------------------------------------------------------ | ---------------- | ------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------ | | createI18n | Factory function | Creates a pre-configured i18next instance with deferred initialization and opinionated defaults. | See the doclet in src/createI18n.ts. | | useI18n | React hook | Triggers initialization for an instance created by createI18n and returns reactive readiness state (isInitialized). | See the doclet in src/useI18n.ts. | | HttpResourcesBackend | i18next backend | Loads translation bundles from HTTP endpoints under a locales/ directory, with optional supported-locale manifest filtering. | See the doclet in src/HttpResourcesBackend.ts. | | FetchOptions, HttpResourcesBackendOptions, I18nInstance, UseI18nResult | Types | Type definitions for the backend, instance brand, and hook return state. | See the respective source files. |

Detailed Reference

The authoritative API documentation already lives in the source doclets for each export. Those doclets include the details that are intentionally not duplicated in this README.