{
	"name": "enyo-ilib",
	"version": "6.0-003",
	"main": "./index.js",
	"description": "iLib plugin for enyo. iLib is a cross-engine library of internationalization (i18n) classes written in pure JS",
	"keywords": [
		"internationalization",
		"i18n",
		"localization",
		"l10n",
		"globalization",
		"g11n",
		"date",
		"time",
		"format",
		"locale",
		"translation"
	],
	"license": "apache2",
	"files": [
		"packedbuffer.js",
		"zoneinfo.js",
		"nodeglue.js",
		"ilib/js",
		"ilib/locale",
		"README.md"
	],
	"devAssets": [
		"ilib/locale/**/*.json"
	]
}

{
	"name": "enyo-ilib",
	"version": "6.0-003",
	"main": "./index.js",
	"description": "iLib plugin for enyo. iLib is a cross-engine library of internationalization (i18n) classes written in pure JS",
	"keywords": [
		"internationalization",
		"i18n",
		"localization",
		"l10n",
		"globalization",
		"g11n",
		"date",
		"time",
		"format",
		"locale",
		"translation"
	],
	"license": "apache2",
	"files": [
		"packedbuffer.js",
		"zoneinfo.js",
		"nodeglue.js",
		"ilib/js",
		"ilib/locale",
		"README.md"
	],
	"assets": [
		"ilib/locale/**/*.json"
	]
}

Include ilib locale data in production builds
ENYO-1913: Include ilib locale data in production builds

We were previously omitting ilib locale data from production
builds, on the assumption that it would be provided by some other
means in the production environment.

We will in fact replace the individually bundled locale data in the
webOS production environment, but better to let that happen in the
webOS build process, so that production app builds targeting non-
webOS targets will still have their data where they need it.

(Also, the first pass at the new build scripts for webOS was not
yet providing the locale data so things weren't working properly.)

Enyo-DCO-1.1-Signed-Off-By: Gray Norton (gray.norton@lge.com)
