node-twitter | Twitter clone with node.js | Runtime Evironment library

The error message is pretty clear, you have a syntax error in your mqtt_rules_definer.js file (You have a missplaced . somewhere in your code). You need to fix this before Node-RED can load it.

The quickest way to find out what line the problem is will be to do something like the following:

• change to the ~/.node-red directory
• run node with no file after the command $ node

• This will start a interactive shell which you can then type in the following:

As mentioned in comment by hardlib,it was actually the issue of DNS lookup and as per link,I was able to solve the same issue.Thus,reiterating those steps to avoid further confusion:

1)Find the DNS pertaining to your system:

after ~3days solved the problem: i should have paid attention to the details

Loopback adds "/api/" in the global config to all API calls. Otherwise, it treats path as a route.

providers.json :

{ "twitter-login": { "provider": "twitter", "authScheme": "oauth", "module": "passport-twitter", "callbackURL": "/api/auth/twitter/callback", "authPath": "/api/auth/twitter", "callbackPath": "/api/auth/twitter/callback", "successRedirect": "/", "failureRedirect": "/login", "consumerKey": "key", "consumerSecret": "key", "failureFlash": true } }

while on the client side I had to add "/api/" to each API call url for example

After searching through and trying many node package finally i got my answer using twit package. I have created direct message stream using twit package like shown in code below.

I made it work. Before I changed my access from "read" to "read, write, and direct messages". And I did regenerate my "consumer key and secret", also "access token and token secret" several times.

It should work, but it wasn't.

At last I totally delete the app on Twitter and recreated it, then it works!

Hope this can help people who met this weird issue.

You can use packages just by including into package.json, using the normal javascript NPM commands (eg npm install -S, check out https://claudiajs.com/tutorials/packaging.html for more information), but based on your code this doesn't seem to be the problem.

• you should return the promise out of the handler. (you're just instantiating the promise, not returning it)
• no need to use bluebird, lambda uses node 4.3 which supports Promises out of the box
• twitter.getRequestToken seems to use a callback, you'll need to translate that back to the promise you're returning and resolve/reject the result. check out an intro on promises somewhere online, or just use denodeify to turn the callback function into a promise directly