Yargs Nynorsk Norwegian Localization File

JSON file with Norwegian Nynorsk translations for yargs CLI library, covering commands, options, examples, errors, and argument validation messages.

n8n
Yargs Nynorsk Norwegian Localization File

This file is a locale JSON for the yargs command-line parser library, providing comprehensive translations into Norwegian Nynorsk (nn). It maps English strings for UI elements like 'Commands:', 'Options:', and 'Examples:' to their Nynorsk equivalents such as 'Kommandoar:', 'Alternativ:', and 'Døme:'. Error messages for common issues like missing arguments, invalid values, and too many non-option arguments are also localized, with plural forms handled via 'one' and 'other' keys.

Key translations include data types ('boolean' to 'boolsk'), requirements ('required' to 'obligatorisk'), and validation feedback ('Invalid JSON config file' to 'Ugyldig JSON konfigurasjonsfil'). This ensures CLI tools built with yargs display user-friendly messages in Nynorsk, improving accessibility for Norwegian speakers.

Benefits include enhanced internationalization for Node.js CLI applications, reducing barriers for non-English users. Use cases: localizing dev tools, scripts, or n8n CLI interfaces in Norwegian projects; integrating into workflows needing multilingual CLI support; or customizing yargs in automation scripts for regional teams. Though static, it saves time on manual translations and ensures consistency.

$2.99
Last updated October 3, 2026
30-day money-back guarantee
Instant download
Lifetime updates included

New buyers can create an account from the cart to unlock a controlled $10 first-purchase credit on eligible orders of $25+.

Secure checkout powered by Stripe

Support

How to import this workflow into n8n

  1. 1Purchase or download the workflow to get the n8n workflow JSON file.
  2. 2In your n8n instance, open Workflows and choose "Import from File" (or paste the JSON with Ctrl+V on the canvas).
  3. 3Open each node marked with a credential warning and connect your own accounts and API keys.
  4. 4Run the workflow once manually to verify the data flow, then toggle it to Active.

Related Other workflows

More from Matt Buds

Need this deployed? We'll set it up for you.

Our automation experts deploy this workflow in your stack, connect your accounts, and verify it works — or build a custom solution from scratch.