Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

google-libphonenumber

Package Overview
Dependencies
Maintainers
1
Versions
129
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

google-libphonenumber - npm Package Compare versions

Comparing version 3.2.5 to 3.2.6

8

CHANGELOG.md
# Changelog
## [v3.2.6](https://github.com/ruimarinho/google-libphonenumber/tree/v3.2.6) (2019-10-18)
[Full Changelog](https://github.com/ruimarinho/google-libphonenumber/compare/v3.2.5...v3.2.6)
**Merged pull requests:**
- Update libphonenumber@8.10.21 [\#216](https://github.com/ruimarinho/google-libphonenumber/pull/216) ([ruimarinho](https://github.com/ruimarinho))
- Update libphonenumber@8.10.20 [\#213](https://github.com/ruimarinho/google-libphonenumber/pull/213) ([ruimarinho](https://github.com/ruimarinho))
## [v3.2.5](https://github.com/ruimarinho/google-libphonenumber/tree/v3.2.5) (2019-09-12)

@@ -4,0 +12,0 @@ [Full Changelog](https://github.com/ruimarinho/google-libphonenumber/compare/v3.2.4...v3.2.5)

2

package.json
{
"name": "google-libphonenumber",
"version": "3.2.5",
"version": "3.2.6",
"description": "The up-to-date and reliable Google's libphonenumber package for node.js.",

@@ -5,0 +5,0 @@ "author": {

@@ -275,2 +275,29 @@ # google-libphonenumber

### Chrome Extensions
Google Closure Compiler API, a serviced provided by Google to compile code online via its Closure library, may not always return fully compliant UTF-8-encoded output.
Loading extensions using this library on Google Chrome and other Chromium-based browsers may result in the following error when compiled with webpack:
`Could not load file 'file.js' for content script. It isn't UTF-8 encoded.`
While the local Java-based version supports a parameter which would let us workaround this issue at the source using `--charset=US-ASCII`, the online API version, which is a lot more convenient to use, does not offer support for an equivalent parameter (e.g. `output_charset=US-ASCII`).
In order to workaround this issue when using webpack, make sure to output US-ASCII characters only when defining `TerserPlugin` options, as demonstrated below:
```js
optimization: {
minimize: process.env.NODE_ENV !== 'development',
minimizer: [
new TerserPlugin({
terserOptions: {
output: {
ascii_only: true
}
},
}),
]
}
```
## Tests

@@ -277,0 +304,0 @@

Sorry, the diff of this file is too big to display

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc