libphonenumber-js - npm Package Compare versions

Comparing version 0.4.32 to 0.4.33

build/parse.js

@@ -6,3 +6,3 @@ 'use strict';
 });
-exports.VALID_PUNCTUATION = exports.VALID_DIGITS = exports.PLUS_CHARS = undefined;
+exports.DIGIT_MAPPINGS = exports.VALID_PUNCTUATION = exports.VALID_DIGITS = exports.PLUS_CHARS = undefined;
 
@@ -117,3 +117,3 @@ var _getIterator2 = require('babel-runtime/core-js/get-iterator');
 // may be used in phone numbers are mapped to a European equivalent.
-var DIGIT_MAPPINGS = {
+var DIGIT_MAPPINGS = exports.DIGIT_MAPPINGS = {
 	'0': '0',
@@ -120,0 +120,0 @@ '1': '1',

custom.js

@@ -6,2 +6,3 @@ 'use strict'
 exports.parse             = require('./build/parse').default
+exports.DIGITS            = require('./build/parse').DIGIT_MAPPINGS
 exports.format            = require('./build/format').default
@@ -8,0 +9,0 @@ exports.get_number_type   = require('./build/get number type').default

es6/parse.js

@@ -91,3 +91,3 @@ import _getIterator from 'babel-runtime/core-js/get-iterator';
 // may be used in phone numbers are mapped to a European equivalent.
-var DIGIT_MAPPINGS = {
+export var DIGIT_MAPPINGS = {
 	'0': '0',
@@ -94,0 +94,0 @@ '1': '1',

index.common.js

@@ -45,2 +45,3 @@ 'use strict'
 exports.DIGIT_PLACEHOLDER = custom.DIGIT_PLACEHOLDER
+exports.DIGITS            = custom.DIGITS
 
@@ -47,0 +48,0 @@ // camelCase aliases

index.es6.js

@@ -69,3 +69,9 @@ import metadata from './metadata.min.json'
 
-export { default as parseCustom }         from './es6/parse'
+export
+{
+	default as parseCustom,
+	DIGIT_MAPPINGS as DIGITS
+}
+from './es6/parse'
+
 export { default as formatCustom }        from './es6/format'
@@ -72,0 +78,0 @@ export { default as isValidNumberCustom } from './es6/validate'

package.json

 {
   "name": "libphonenumber-js",
-  "version": "0.4.32",
+  "version": "0.4.33",
   "description": "A simpler (and smaller) rewrite of Google Android's popular libphonenumber library",
@@ -35,3 +35,5 @@ "main": "index.common.js",
     "metadata:publish": "npm version patch && npm publish && git push",
-    "metadata:update": "npm run metadata:branch && npm run metadata:download && babel-node runnable/update && npm run metadata:unbranch",
+    "metadata:update:release": "babel-node runnable/metadata-update-and-release",
+    "metadata:update:branch": "npm run metadata:branch && babel-node runnable/metadata-update-and-push",
+    "metadata:update:pull-request": "npm run metadata:branch && babel-node runnable/metadata-update-and-push-and-pull-request",
     "metadata:generate": "npm-run-all metadata:generate:min metadata:generate:full metadata:generate:mobile",
@@ -38,0 +40,0 @@ "metadata:generate:min": "babel-node -- runnable/generate ../PhoneNumberMetadata.xml ../metadata.min.json",

README.md

@@ -192,10 +192,10 @@ # libphonenumber-js
 
-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:
+Currently I have a script set up monitoring changes to `PhoneNumberMetadata.xml` in Google's repo and automatically releasing new versions of this library when metadata in Google's repo gets updated. So this library'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:
 
   * Fork this repo
   * `npm install`
-  * `npm run metadata:update`
+  * `npm run metadata:update:branch`
   * 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, 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.
+`npm run metadata:update:branch` 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.
 
@@ -339,3 +339,3 @@ 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.
 
-A daily (24 * 60 * 60) `launchd` job
+Create a daily (24 * 60 * 60) `launchd` job
 
@@ -342,0 +342,0 @@ http://alvinalexander.com/mac-os-x/mac-osx-startup-crontab-launchd-jobs

runnable/metadata-branch.js

@@ -1,8 +0,3 @@
-var child_process = require('child_process')
+var exec = require('./modules/exec')
 
-function exec(command)
-{
-	return child_process.execSync(command).toString().trim()
-}
-
 let metadata_branch_exists = false
@@ -9,0 +4,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

New author

Supply chain risk

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

1965598

increased by0.13%

Number of package files

69

increased by4.55%

Lines of code

5878

increased by0.65%

Number of medium supply chain risk alerts

4

decreased by-50%

Worsened metrics

Published versions last week

0

decreased by-100%

No dependency changes