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

@nexure/wti-middleware

v2.0.0

Published

Fetch translations from your webTranslate it project into your app

Downloads

5

Readme

WTI-middleware

Fetch translations from your webTranslate it project into your app

Usage

V 2

From version 2 you can return a plain function which takes the locale as an argument breaking changes wti function now takes an object with properties instead of a list of arguments

// as middleware
import wti from 'wti-middleware'
const middleware = wti({
  projectToken: 'WTI_PROJECT_KEY',
  ttl: 60*5 // in seconds, optional
  plainFunction: false // return plain function, optinal
})

app.use((req, res, next) => {
  req.headers.wti_locale = 'en-US'
  next()
})

app.use(middleware)

// as plain function
import wti from 'wti-middleware'
const fun = wti({
  projectToken: 'WTI_PROJECT_KEY',
  plainFunction: true // return plain function, optinal
})

const translations = await fun('en-US')

V 1.X

This middleware needs a request header with the current locale to work properly

The middleware factory function takes 2 parameters, your WTI read key and an optional TTL in seconds for cache

import wti from 'wti-middleware'
const middleware = wti('WTI_READ_KEY')

app.use((req, res, next) => {
  req.headers.wti_locale = 'en-US'
  next()
})
app.use(middleware)

The middleware will add a translation property to your request object

...
app.use(middleware)
app.use((req, res, next) => {
  const { translations } = req
  // do stuff
})