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

nuxt-i18n-link

v1.0.3

Published

A convenient replacement for <nuxt-link> component when using nuxt-i18n

Downloads

135

Readme

nuxt-i18n-link

A convenient replacement for <nuxt-link> component when using nuxt-i18n. It is simply a replacement for this exact code:

<nuxt-link :to="localePath("/page")">
	Link
</nuxt-link>

into

<nuxt-i18n-link to="/page">
	Link
</nuxt-i18n-link>

This prevents the mistake of omitting localePath() that would often fall under the radar. More details

Usage

Install with

npm i nuxt-i18n-link

Note: Add --save if npm < 5.0.0

Then nuxt.config.js

{
	modules: [
		'nuxt-i18n-link'
	]
}

Finally, use like

<nuxt-i18n-link to="/page" lang="en">
	Link
</nuxt-i18n-link>

// or

<nuxt-i18n-link to="{ path: '/page', hash: '#conclusion'}" lang="en">
	Link
</nuxt-i18n-link>

For more details, see router-link.

Props

|Name |Type |Default |Required|Description | |--------|----------------|----------|--------|-----------------------------| |to |string | object|- | [x] |Destination Route (see router-link) | |lang |string |undefined | [ ] |Two-letter ISO language code |

Motivation

The use of localePath() in <nuxt-link> is necessary for Nuxt.js projects that use nuxt-i18n.

To demonstrate, say a project has two routes:

  1. Home page /
  2. About page /about

Using nuxt-i18n, these routes will become

| |English |French | |--------|-----------|-----------| |/ |/en/ |/fr/ | |/about|/en/about|/fr/about|

However, <nuxt-link to="/about"> will not route to /en/about nor /fr/about but to /about which does not exist anymore. The documented solution to this is to use localePath() as <nuxt-link :to="localePath('/about')">, which will route to /en/about or /fr/about according to the current language.

The documented solution is easily forgotten, and <nuxt-link to="about"> will not produce any errors when a default language is defined. Moreover, the error is not immediately obvious unless the non-default languages are being tested.

Hence, <nuxt-i18n-link> was made.

MIT License