Security News
pnpm 10.0.0 Blocks Lifecycle Scripts by Default
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
@googlemaps/addressvalidation
Advanced tools
client for Node.js
A comprehensive list of changes in each version may be found in the CHANGELOG.
Read more about the client libraries for Cloud APIs, including the older Google APIs Client Libraries, in Client Libraries Explained.
Table of contents:
npm install @googlemaps/addressvalidation
/**
* This snippet has been automatically generated and should be regarded as a code template only.
* It will require modifications to work.
* It may require correct/in-range values for request initialization.
* TODO(developer): Uncomment these variables before running the sample.
*/
/**
* Required. The address being validated. Unformatted addresses should be
* submitted via `address_lines` google.type.PostalAddress.address_lines.
* The total length of the fields in this input must not exceed 300
* characters.
* Supported regions can be found in the
* FAQ (https://developers.google.com/maps/documentation/address-validation/faq#which_regions_are_currently_supported).
* The language_code google.type.PostalAddress.language_code value in the
* input address is reserved for future uses and is ignored today. The
* validated address result will be populated based on the preferred language
* for the given address, as identified by the system.
* The Address Validation API ignores the values in
* recipients google.type.PostalAddress.recipients and
* organization google.type.PostalAddress.organization. Any values in those
* fields will be discarded and not returned. Please do not set them.
*/
// const address = {}
/**
* This field must be empty for the first address validation request. If
* more requests are necessary to fully validate a single address (for
* example if the changes the user makes after the initial validation need to
* be re-validated), then each followup request must populate this field with
* the
* response_id google.maps.addressvalidation.v1.ValidateAddressResponse.response_id
* from the very first response in the validation sequence.
*/
// const previousResponseId = 'abc123'
/**
* Enables USPS CASS compatible mode. This affects _only_ the
* google.maps.addressvalidation.v1.ValidationResult.usps_data field of
* google.maps.addressvalidation.v1.ValidationResult. Note: for USPS CASS
* enabled requests for addresses in Puerto Rico, a
* google.type.PostalAddress.region_code of the `address` must be provided
* as "PR", or an google.type.PostalAddress.administrative_area of the
* `address` must be provided as "Puerto Rico" (case-insensitive) or "PR".
* It's recommended to use a componentized `address`, or alternatively specify
* at least two google.type.PostalAddress.address_lines where the first line
* contains the street number and name and the second line contains the city,
* state, and zip code.
*/
// const enableUspsCass = true
// Imports the Addressvalidation library
// eslint-disable-next-line node/no-missing-require
const {AddressValidationClient} = require('@googlemaps/addressvalidation').v1;
// Instantiates a client
const addressvalidationClient = new AddressValidationClient();
async function callValidateAddress() {
// Construct request
const request = {
address: {
regionCode: 'US',
addressLines: ['1600 Amphitheatre Pkwy', 'Mountain View CA 94040'],
},
};
// Run request
const response = await addressvalidationClient.validateAddress(request);
console.log(response);
}
callValidateAddress();
Samples are in the samples/
directory. Each sample's README.md
has instructions for running its sample.
Sample | Source Code | Try it |
---|---|---|
Address_validation.provide_validation_feedback | source code | |
Address_validation.validate_address | source code | |
Quickstart | source code |
The Address Validation API Node.js Client API Reference documentation also contains samples.
Our client libraries follow the Node.js release schedule. Libraries are compatible with all current active and maintenance versions of Node.js. If you are using an end-of-life version of Node.js, we recommend that you update as soon as possible to an actively supported LTS version.
Google's client libraries support legacy versions of Node.js runtimes on a best-efforts basis with the following warnings:
Client libraries targeting some end-of-life versions of Node.js are available, and
can be installed through npm dist-tags.
The dist-tags follow the naming convention legacy-(version)
.
For example, npm install @googlemaps/addressvalidation@legacy-8
installs client libraries
for versions compatible with Node.js 8.
This library follows Semantic Versioning.
This library is considered to be stable. The code surface will not change in backwards-incompatible ways unless absolutely necessary (e.g. because of critical security issues) or with an extensive deprecation period. Issues and requests against stable libraries are addressed with the highest priority.
More Information: Google Cloud Platform Launch Stages
Contributions welcome! See the Contributing Guide.
Please note that this README.md
, the samples/README.md
,
and a variety of configuration files in this repository (including .nycrc
and tsconfig.json
)
are generated from a central template. To edit one of these files, make an edit
to its templates in
directory.
Apache Version 2.0
See LICENSE
FAQs
client for Node.js
The npm package @googlemaps/addressvalidation receives a total of 8,301 weekly downloads. As such, @googlemaps/addressvalidation popularity was classified as popular.
We found that @googlemaps/addressvalidation demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
Product
Socket now supports uv.lock files to ensure consistent, secure dependency resolution for Python projects and enhance supply chain security.
Research
Security News
Socket researchers have discovered multiple malicious npm packages targeting Solana private keys, abusing Gmail to exfiltrate the data and drain Solana wallets.