wrangr / awis Goto Github PK

The dependency aws4 was updated from 1.8.0 to 1.9.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

aws4 is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Thank you for this great library!

We currently use awis (v1.0.10) to query the sites by categories (Action: 'CategoryListings') in our project.

We noticed that it only works with the 'us-west-1' region. With the other regions (e.g. us-west-2), we always receive the error messages as follows

Error: getaddrinfo ENOTFOUND awis.us-west-2.amazonaws.com awis.us-west-2.amazonaws.com:443
   at errnoException (dns.js:50:10)
   at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:92:26)

Im currently getting an Failed to load https://awis.amazonaws.com/...: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:3000' is therefore not allowed access. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

It looks like Amazon isn't passing a Access-Control-Allow-Origin header, so can we have the ability to set a no-cors in our request?

Hi,
I have just received the following e-mail from Amazon Web Services:

I have noticed that this package uses the http endpoint:

    Request({
      url: 'http://' + apiDomain,
      qs: internals.query(req, apiDomain, options)
    }, (err, res) => {

index.js:L171

Can I submit a PR to update the package to use the https endpoint? @lupomontero

The dependency lodash was updated from 4.17.10 to 4.17.11.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

lodash is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Hi,

I sometimes get failures :

TypeError: Cannot read property '0' of undefined
  at /Users/romain/work/campaygn-ng/node_modules/awis/index.js:40:44
  at Parser.<anonymous> (/Users/romain/work/campaygn-ng/node_modules/awis/node_modules/xml2js/lib/xml2js.js:368:20)
  at Parser.EventEmitter.emit (events.js:95:17)
  at Object.saxParser.onclosetag (/Users/romain/work/campaygn-ng/node_modules/awis/node_modules/xml2js/lib/xml2js.js:338:24)
  at emit (/Users/romain/work/campaygn-ng/node_modules/awis/node_modules/xml2js/node_modules/sax/lib/sax.js:615:33)
  at emitNode (/Users/romain/work/campaygn-ng/node_modules/awis/node_modules/xml2js/node_modules/sax/lib/sax.js:620:3)
  at closeTag (/Users/romain/work/campaygn-ng/node_modules/awis/node_modules/xml2js/node_modules/sax/lib/sax.js:861:5)
  at Object.write (/Users/romain/work/campaygn-ng/node_modules/awis/node_modules/xml2js/node_modules/sax/lib/sax.js:1293:29)
  at Parser.exports.Parser.Parser.parseString (/Users/romain/work/campaygn-ng/node_modules/awis/node_modules/xml2js/lib/xml2js.js:386:29)
  at Parser.parseString (/Users/romain/work/campaygn-ng/node_modules/awis/node_modules/xml2js/lib/xml2js.js:6:61)
  at Object.exports.parseString (/Users/romain/work/campaygn-ng/node_modules/awis/node_modules/xml2js/lib/xml2js.js:409:19)
  at parse (/Users/romain/work/campaygn-ng/node_modules/awis/index.js:33:10)
  at Request._callback (/Users/romain/work/campaygn-ng/node_modules/awis/index.js:72:7)
  at Request.self.callback (/Users/romain/work/campaygn-ng/node_modules/request/request.js:121:22)
  at Request.EventEmitter.emit (events.js:98:17)
  at Request.<anonymous> (/Users/romain/work/campaygn-ng/node_modules/request/request.js:978:14)
  at Request.EventEmitter.emit (events.js:117:20)
  at IncomingMessage.<anonymous> (/Users/romain/work/campaygn-ng/node_modules/request/request.js:929:12)
  at IncomingMessage.EventEmitter.emit (events.js:117:20)
  at _stream_readable.js:920:16
  at process._tickDomainCallback (node.js:459:13)

This is not on any particular URL, this appears to be really random.
I tried to investigate furthermore, but did not came closer to an explanation, as digging into sax is kind of an ultimate pain for me.

When I tried to query the path: Top/Shopping/Clothing/Children's, it gave me an error:
error: err Error: SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml
• The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

Hey guys,
Just got this e-mail from AWS stating that root IAM account keys will no longer work for authenticating against AWIS.

AWIS will start requiring an AWIS-policy-granted IAM user instead of the root account user, but only through its Auth v4 API.

Seeing as this package does not use the Auth v4 way of authenticating against AWIS (with the Authorization header), this is a breaking change and AWS has only granted about 40 days for us to comply with it.

An example Auth v4 request is detailed here:
http://docs.aws.amazon.com/AlexaWebInfoService/latest/ApiReference_UrlInfoAction.html

The e-mail from AWS:

Hello,

In accordance with AWS security guidelines, the Alexa Web Information Service and Alexa Top Sites API’s now support the use of IAM credentials. The support for using root account credentials to access these services will be discontinued on January 31, 2018.

In order to continue using the Alexa Web Information Service and Alexa Top Sites services, you will be required to create an IAM user in your AWS account and make slight code changes anywhere your applications make calls to these API’s. Our code samples (AWIS[1], Alexa Top Sites[2]) and documentation (AWIS[3], Alexa Top Sites[4]) have been updated to reflect these changes.

Migration to the new request format must be completed by January 31, 2018.

If you have any questions or concerns about these changes, you have 2 options for contacting Alexa.com support:

1. If you have an Alexa.com account, please login to https://www.alexa.com/help and submit a help request.
2. Post to the relevant API forum (AWIS, Alexa Top Sites).

We apologize for any inconvenience this may cause. Thank you for your continued use of Alexa's API and for helping us make this service more secure.

[1] https://aws.amazon.com/code/AWIS
[2] https://aws.amazon.com/code/Alexa-Top-Sites/
[3] https://aws.amazon.com/documentation/awis/
[4] https://aws.amazon.com/documentation/alexa-top-sites/

Sincerely,
Amazon Web Services

@lupomontero Is modifying this library to work with Auth v4 feasible? Is this something you would have time to do?

I want to use amazon web information services to fetch the website traffic data.
But I am not sure where to include the IAM user access key id and secret access key in awis node module.
Can you please provide a working example?

Got an email notification from amazon that they're shutting down their Alexa http endpoint on Aug 24th and only allowing for requests to their https endpoint .. just wondering which endpoint you're using in this module?

var awis = require('awis');

var client = awis({
  key: config['AWS_ACCESS_KEY_ID'],
  secret: config['AWS_SECRET_ACCESS_KEY']
});

client({
   'Action': 'UrlInfo',
   'Url': 'cnn.com',
   'ResponseGroup': 'Related,TrafficData,ContentData'
}, function (err, data) {
   console.log(data);
   console.log(err);
});

I don't understand. I also generated new access key ID and secret access key, but same result.

Any tips?

The dependency xml2js was updated from 0.4.19 to 0.4.20.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

xml2js is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

the API returns:

{
  "trafficData": {
    "dataUrl": "google.com/",
    "rankByCountry": {
      "country": [
        {
          "rank": "6",
          "contribution": {
            "pageViews": "0.5%",
            "users": "0.5%"
          }
        },
        {
          "rank": "2",
          "contribution": {
            "pageViews": "13.0%",
            "users": "9.1%"
          }
        },
        ...

These results are missing country code information.

Version 3.4.0 of mocha just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Why TopSites is not supported?

The dependency request was updated from 2.88.0 to 2.88.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

request is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Version 10.1.0 of eslint-config-hapi just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-config-hapi is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴