npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@saeris/mini-movie-db-api

v2.0.4

Published

A GraphQL API wrapper for The Movie DB built with Apollo Data Sources

Downloads

11

Readme

🛠️ Setup

Install dependencies by running yarn, then create a new file in the root directory named .env. You'll need to get an API key from The Movie DB in order to run any queries. For more information, please read the Movie DB docs. Additionally, if you want to track usage metrics for your API, you'll need to get an API key from Apollo Graph Manager. For instructions on how to do that, please read the Apollo Graph Manager docs. In your new .env file, copy + paste the following and replace the text following the = sign with your newly create API keys.

MOVIE_DB_API_KEY=<insert your movie database api key here>
ENGINE_API_KEY=<insert your apollo graph manager api key here>

Once that's done, you can now start up a development server using yarn start. By default this will use Serverless Offline, but if you would instead like to use Netlify Lamba, you can run yarn start:netlify instead. Once the development server is listening, you can pull up a GraphQL Playground by visiting one of the following URLs:

Lambda: http://localhost:1337/dev Netlify: http://localhost:1337/.netlify/functions/mini-movie-db-api

🕹️ Demo

You can try out the API using the GraphQL Playground hosted at https://mini-movie-db-api.saeris.io/.netlify/functions/mini-movie-db-api

🧪 Testing

Testing is provided via jest and is pre-configured to run with codecov as well. While tests for this project are far from complete, they can be found under src/__TEST__ and follow a naming format of [filename].spec.ts. Additionally, this project uses eslint, typescript, and prettier, all three of which are automatically run on each commit via husky + lint-staged. To manually lint and test, use the following commands:

Lint:

yarn lint

Typecheck:

yarn typecheck

Test and watch for changes:

yarn test:watch

Lint + Typecheck + Test:

yarn test

🚢 Deployment

To deploy the server, you'll need to follow the Serverless Framework's Setup Guide to deploy to AWS. If you'd rather use Netlify, you'll need to follow whichever method works best for your workflow. Refer to Netlify's Docs for more information.

If you're deploying to AWS, you can use the following commands to deploy to Staging or Production:

Staging:

yarn deploy

Production:

yarn deploy:prod

Alternatively, if you're using Travis CI, you can deploy to both on each commit as part of your CI process by uncommenting the following lines inside travis.yml:

deploy:
 # deploy develop to the staging environment
 - provider: script
   skip_cleanup: true
   script: yarn deploy:dev
   on:
     node: "12"
     branch: develop
 # deploy master to production
 - provider: script
   skip_cleanup: true
   script:
     - yarn deploy:prod
   on:
     node: "12"
     branch: master

🥂 License

Released under the MIT license.