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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@laserfiche/lf-resource-library

v5.0.0

Published

a library containing resource files that can be used in conjunction with LfLocalizationService from `@laserfiche/lf-js-utils`

Downloads

52

Readme

Introduction

Contains resource files that can be used in conjunction with LfLocalizationService from @laserfiche/lf-js-utils.

Creating a new resource

  1. Create a folder under resources (e.g. my-new-resources)
  2. In that folder create a resource file for each supported language.
  3. The file name should be in the format languagecode2-country/regioncode2. languagecode2 is a lowercase two-letter code derived from ISO 639-1. country/regioncode2 is derived from ISO 3166 and usually consists of two uppercase letters, or a BCP-47 language tag. codes. The file should have an extension of .json
    • en-US.json
    • zh-Hans.json
  4. Required/Default Language: en.json
    • If a resource key is not found in the selected language, the en string will be used.
  5. Optional Language: For Laserfiche, we recommend providing resources for at least: ar-EG, en-US, en-GB, es-MX, fr-CA, fr-FR, pt-BR, zh-Hans, zh-Hant

Documentation

With LfLocalizationService from @laserfiche/lf-js-utils

LfLocalizationService is a service that handles internationalization and localization, mapping text to its corresponding translated texts in the selected language. @laserfiche/lf-resource-library provides language resources files in JSON that can be utlized by LfLocalizationService.

Install @laserfiche/lf-js-utils:

npm install  @laserfiche/lf-js-utils

Import LfLocalizationService:

import { LfLocalizationService } from "@laserfiche/lf-js-utils";

In node, import any fetch polyfill which suits your requirements: examples:

Example Usages:

let localizationService = new LfLocalizationService();
localizationService.setLanguage('es-MX');
await localizationService.initResourcesFromUrlAsync('https://cdn.jsdelivr.net/npm/@laserfiche/lf-resource-library@4/resources/laserfiche-base');
let loading =  localizationService.getString('LOADING'); // loading -> 'Cargando...'

Icons

[Example Usages]

 export function getDocumentIconUrlFromIconId(iconId: string): string {
    return `https://cdn.jsdelivr.net/npm/@laserfiche/lf-resource-library@4/resources/icons/document-icons.svg#${iconId}`;
}

Change Log

See CHANGELOG here.

Contribution

We welcome contributions and feedback. Please follow our contributing guidelines.