aws-sdk-js VS twitter-api-client

⚠️Here's the issue: https://github.com/aws/aws-sdk-js/issues/4519

The updates could be parsed from the github repo's CHANGELOG files (ex: javascript, java, python). I'm picturing an RSS feed generated for a specific language and module (ex: python s3, javascript s3, java sqs)

Another option is to look at the changelog for the AWS SDK. Because the AWS SDK has to have support for pretty much every service ever it gets a new version and a changelog whenever new things are added. I like to refer to this changelog from time to time: https://github.com/aws/aws-sdk-js/blob/master/CHANGELOG.md

From this thread I double-checked that all query strings and the origin, Access-Control-Request-Method and Access-Control-Request-Headers are sent to the origin (I ran into some signature mismatch issues before that were solved with this origin request policy).

Now that you have installed MinIO server, let's use it on your project. I will be using the official S3 JavaScript SDK as example. But should be applicable for all other S3 SDKs.

The client is only available for Java and Python. https://github.com/aws/aws-sdk-js/issues/1164

The best way I've found to locate the X-Amz-Target value is from this AWS support ticket where it is recommend to look at the SDK docs for the service and locate the targetPrefix field in the metadata.

I wonder if there's a way to only bring in the S3 SDK from aws-sdk to help trim the file size. I believe there might be a way to import only certain files, maybe something like this?

Due to performance reasons, one of the goals was to switch to rollup for bundling all our applications, however, we use webpack due to rollup’s known issues with aws-sdk.

Maybe this?

const mokkappsTwitterId = 481186762; const searchQuery = 'mokkapps'; const searchResultCount = 100; const fetchRecentTweets = async secretValues => { // Configure Twitter API Client const twitterClient = new twitterApiClient.TwitterClient({ apiKey: secretValues.TWITTER_API_KEY, apiSecret: secretValues.TWITTER_API_KEY_SECRET, accessToken: secretValues.TWITTER_ACCESS_TOKEN, accessTokenSecret: secretValues.TWITTER_ACCESS_TOKEN_SECRET, }); // Trigger search endpoint: https://github.com/FeedHive/twitter-api-client/blob/main/REFERENCES.md#twitterclienttweetssearchparameters const searchResponse = await twitterClient.tweets.search({ q: searchQuery, count: searchResultCount, result_type: 'recent', }); // Access statuses from response const statuses = searchResponse.statuses; };

To be able to fetch the follower count from Twitter API I decided to use FeedHive’s Twitter Client. This library needs four secrets to be able to access Twitter API. We will store them in the AWS Secret Manager, my article “How to Use Environment Variables to Store Secrets in AWS Amplify Backend” will guide you through this process.

twitter api client

Although, that's not the full story. Because I did make a very primitive scheduler for personal use, back in August/September, and that's where I created the Open-Source project twitter-api-client which is a NodeJS client for interacting with the Twitter API. This client is now a core module of FeedHive.

In the first two parts of this tutorial, we went over how to create a Twitter bot that sends out tweets from the Today in History API and then created scheduled tasks that make sure these tweets are tweeted automatically at certain times of the day. We are using twitter-api-client to easily connect to the Twitter API. You can see the bot for this tutorial in live action on @HistoryBot7.

We're going to be using the twitter-api-client to interact with the Twitter API more seamlessly.