libphonenumber-js - npm Package Compare versions

Comparing version 0.2.26 to 0.2.27

build/validate.js

@@ -17,2 +17,6 @@ 'use strict';
 function is_valid(parsed, country_code) {
+	if (!parsed) {
+		return false;
+	}
+
 	if (typeof parsed === 'string') {
@@ -19,0 +23,0 @@ parsed = _parse2.default.call(this, parsed, country_code);

package.json

 {
   "name": "libphonenumber-js",
-  "version": "0.2.26",
+  "version": "0.2.27",
   "description": "A simpler (and smaller) rewrite of Google Android's popular libphonenumber library",
@@ -5,0 +5,0 @@ "main": "index.common.js",

README.md

@@ -166,3 +166,3 @@ # libphonenumber-js
 
-Currently I have a daily bash script set up monitoring the changes to `PhoneNumberMetadata.xml` in Google's repo and it automatically creates a Pull Request when the metadata is updated. So this project's metadata is supposed to be up-to-date. Still, in case the automatic metadata update script malfunctions some day, anyone can request metadata update via a Pull Request here on GitHub:
+Currently I have an npm script for monitoring changes to `PhoneNumberMetadata.xml` in Google's repo and automatically creating a Pull Request in this repo with the fresh metadata when it is updated. What's left is to test this script and schedule it to run daily on my machine. So this project's metadata is supposed to be up-to-date. Still, in case the automatic metadata update script malfunctions some day, anyone can request metadata update via a Pull Request here on GitHub:
 
@@ -172,7 +172,7 @@ * Fork this repo
   * `npm run metadata:update`
-  * Submit a Pull Request to the main repo from the `update-metadata` branch of your fork
+  * Submit a Pull Request to this repo from the `update-metadata` branch of your fork
 
-`npm run metadata:update` command creates a new `update-metadata` branch, downloads the new [`PhoneNumberMetadata.xml`](https://github.com/googlei18n/libphonenumber/blob/master/resources/PhoneNumberMetadata.xml) into the project folder replacing the old one, generates JSON metadata out of the XML one, runs the tests, commits the new metadata and pushes the commit to the remote `update-metadata` branch of your fork.
+`npm run metadata:update` command creates a new `update-metadata` branch, downloads the new [`PhoneNumberMetadata.xml`](https://github.com/googlei18n/libphonenumber/blob/master/resources/PhoneNumberMetadata.xml) into the project folder replacing the old one, generates JSON metadata out of the XML one, checks if the metadata has changed, runs the tests, commits the new metadata and pushes the commit to the remote `update-metadata` branch of your fork.
 
-Alternatively, a developer may wish to update metadata urgently, without waiting for a pull request approval. In this case just perform the steps described in the [Customizing metadata](#customizing-metadata) section of this document (just don't pass the `--countries` option).
+Alternatively, a developer may wish to update metadata urgently, without waiting for a pull request approval. In this case just perform the steps described in the [Customizing metadata](#customizing-metadata) section of this document.
 
@@ -179,0 +179,0 @@ ## React

source/validate.js

@@ -11,2 +11,7 @@ import parse, { get_number_type } from './parse'
 {
+	if (!parsed)
+	{
+		return false
+	}
+
 	if (typeof parsed === 'string')
@@ -13,0 +18,0 @@ {

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

1136063

increased by0.03%

Lines of code

5025

increased by0.14%

No dependency changes