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

mediql

v1.0.6

Published

mediql npm package

Downloads

14

Readme

mediql-npm-package

MediQL is a GraphQL developer tool, built to work on top of GraphiQL, an open-source web-based integrated development environment (IDE). MediQL takes it a step further by delivering query response visualization, error indication, and the ability to observe original external API response objects which GraphiQL can not.

The mediql package contains only the functionality necessary to deliver a developer's resolved external API responses as well as the GraphQL query response to MediQL's server.

Note: this package is strictly for development mode.

Usage

  • [ ] In your application's GraphQL Schema file or your file with resolvers...
  • [ ] Import the postOriginResp function from the mediql package using CommonJS module syntax.
  • [ ] Invoke the postOriginResp function inside each of your resolvers with specific arguments shown below:
//import the postOriginResp function from the mediql package
const { postOriginResp } = require('mediql');

const {
  GraphQLObjectType,
  GraphQLString,
  GraphQLSchema,
} = require("graphql");

const RootQuery = new GraphQLObjectType({
  name: "RootQueryType",
  fields: {
    Movie: {
      type: SwapiMovieType,
      args: { id: { type: GraphQLString } },
      async resolve(parent, args, context, info) {
        try {

//declare the response variable assign it to the result of your fetch request to the external api url of your choice
          const response = await fetch(
            `https://swapi.dev/api/films/${args.id}`,
            {
              headers: { "content-type": "application/json" },
            }
          );

//declare the parsedResponse variable as the parsed JSON response of your previous response variable
          const parsedResponse = await response.json();
          
//invoke mediql's packaged function with the arguments of response, parsedResponse, and info respectively.
          postOriginResp(response, parsedResponse, info);

          return parsedResponse;
        } catch (err) {
          console.error("Error fetching movie:", err);
          throw new Error("Unable to fetch movie");
        }
      },
    },
  },
});

module.exports = new GraphQLSchema({
  query: RootQuery,
});
  • [ ] In your application's server file...
  • [ ] Import the postQueryResp function from the mediql package using CommonJS module syntax.
  • [ ] Import the graphqlHTTP function from the express-graphql package.
  • [ ] Set up a route at the endpoint /graphql using Express and use the graphqlHTTP() middleware with arguments of schema which was declared beforehand, graphiql which enables GraphiQL, context, and extensions to be able to call the postQueryResp function.
const express = require("express");

//Import the graphqlHTTP function from the express-graphql package
const { graphqlHTTP } = require("express-graphql");

//Import the postQueryResp function from the mediql package
const { postQueryResp } = require("mediql");

const app = express();

//Import your GraphQL schema file and declare it as the variable schema
const schema = require("./schema/schema.js");

const cors = require("cors");
app.use(cors());
app.use(express.json())
const PORT = 3900;

//Set up the /graphql route (i.e.: http://localhost:${PORT}/graphql)
app.use(
  "/graphql",
  graphqlHTTP({
    schema,
    graphiql: true,
    context: ({ req }) => ({ req }),
    extensions: async (
      { document, variables, operationName, result }) => {
      
//Invoke postQueryResp with result argument
      postQueryResp(result);
    },
  })
);

app.listen(PORT, console.log(`Server running on port ${PORT}`));

Documentation

See https://github.com/oslabs-beta/MediQL#readme

Co-Creators