@wordpress/i18n
Advanced tools
Comparing version 3.1.0 to 3.1.1
@@ -1,2 +0,2 @@ | ||
## 3.1.0 (Unreleased) | ||
## 3.1.0 (2018-11-15) | ||
@@ -3,0 +3,0 @@ ### Enhancements |
{ | ||
"name": "@wordpress/i18n", | ||
"version": "3.1.0", | ||
"version": "3.1.1", | ||
"description": "WordPress internationalization (i18n) library.", | ||
@@ -33,9 +33,6 @@ "author": "The WordPress Contributors", | ||
}, | ||
"devDependencies": { | ||
"benchmark": "^2.1.4" | ||
}, | ||
"publishConfig": { | ||
"access": "public" | ||
}, | ||
"gitHead": "a177dd725495d102d24aee87394c724985bd9f72" | ||
"gitHead": "c59ef56fe16bdcc1fffd70b6e8a2fda4bf9c28fe" | ||
} |
@@ -30,3 +30,3 @@ # Internationalization (i18n) | ||
You can use the [WordPress i18n babel plugin](../babel-plugin-makepot/README.md) to generate a `.pot` file containing all your localized strings. | ||
You can use the [WordPress i18n babel plugin](/packages/babel-plugin-makepot/README.md) to generate a `.pot` file containing all your localized strings. | ||
@@ -33,0 +33,0 @@ The package also includes a `pot-to-php` script used to generate a php files containing the messages listed in a `.pot` file. This is useful to trick WordPress.org translation strings discovery since at the moment, WordPress.org is not capable of parsing strings directly from JavaScript files. |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
0
64281