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

@salesforce/i18n

v0.0.21

Published

@salesforce/i18n reference implementation

Downloads

828

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

lwc-adminlwc-admindme722dme722nolanlawsonnolanlawsonire-npm-team-userire-npm-team-userjburniejburnieabirchfieldsfdcabirchfieldsfdcdlouvtondlouvtonmobifymobifyjmsjtujmsjtujasonschroeder-sfdcjasonschroeder-sfdcpackagellamapackagellamamawardmawarddanielshoxdanielshoxduane.chewduane.chewdferrodferrojcourtnerjcourtnerjye-sfjye-sfadirasanamadirasanamhkiihkiiiamaziziamazizdbreese-salesforcedbreese-salesforceashokrudrarajuashokrudrarajudhersamdhersamdemianbrechtdemianbrechtmbettiombettiodamilareolowoniyidamilareolowoniyimmadialaganmmadialaganmjrustmjrustsalesforce-releasessalesforce-releaseskevinv11nkevinv11nbyaobyaopmdartuspmdartusekashidaekashidaravi.jayaramapparavi.jayaramappaapapkoapapkojleen-sfdcjleen-sfdcjqianjqiancwallsfcwallsfdhagberg-sfdhagberg-sfkhawkinskhawkinsamphroamphrojodarovejodarovesfdctakasfdctakafernomacfernomacjimjagjimjagivarleyivarleyjbartolotta-sfdcjbartolotta-sfdccaridycaridy

Keywords

Readme

@salesforce/i18n scoped module

Reference implementation of @salesforce/i18n modules for all locales. A custom module loader is required to provision the appropriate locale-specific module.

Static modules are generated for all locales and available in dist/. Locales available on Salesforce Platform are exposed using lwc.config.json.

Typescript Interface

Refer to the dist/types/index.d.ts for Typescript interfaces for all @salesforce/i18n modules.

Module Naming

It is expected that consumers reference @salesforce/i18n modules in a locale-agnostic manner and rely on the module loader to provision the locale-appropriate implementation.

Locales available on Salesforce Platform are exposed using lwc.config.json with the naming scheme @salesforce/i18n/{module name}/{locale}.

For example, @salesforce/i18n/dir for locale es-SV is exposed as @salesforce/i18n/dir/es-SV.

A module loader may use this mapping to provision the locale-appropriate implementation.