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

@amazeelabs/gatsby-fragments

v1.2.18

Published

Generates fragment.ts files from .gql files to append vendor prefix.

Downloads

241

Readme

Gatsby fragments

Generates *.fragment.ts files from *.gql files to use a vendor prefix.

This is necessary to execute equivalent GraphQL queries on the backend (Drupal) and the frontend (Gatsby) for use cases like instant preview.

Execute one time

npx @amazeelabs/gatsby-fragments generate --path "path/to/fragment-files"

Setup on a project

  1. Decide which fragments should be used by both backend and frontend (typically: content types, media, ...)
  2. Move these fragments in a dedicated directory, e.g. src/fragments/commons
  3. Convert possibly existing Gatsby GraphQL Drupal .ts fragment files to vendor agnostic .gql files
  4. Gitignore the generated *.fragment.ts files from this common directory
  5. Setup the generate fragments script in Gatsby package.json. Example: "generate-fragments": "node gatsby-fragments generate --path './src/fragments/commons' && eslint \"./src/fragments/commons/**/*.fragment.ts\" --fix && prettier --write \"./src/fragments/commons/**/*.fragment.ts\"",
  6. This script could be added to the codegen one, but it needs to be executed first, so generated fragments can then be used by codegen. Example: "codegen": "pnpm generate-fragments && graphql-codegen --config codegen.yml"
  7. Fragments in the common directory can now be executed by both Gatsby and Drupal GraphQL

Step 3. example:

Sample existing Drupal Gatsby specific fragment

import { graphql } from 'gatsby';

export const fragment = graphql`
  fragment ContentPage on DrupalContentPage {
    __typename
    drupalId
    langcode
    title
    articleReference {
      ... on DrupalContentArticle {
        drupalId
        langcode
        title
      }
    }
  }
`;

Becomes GraphQL vendor agnostic

fragment ContentPage on ContentPage {
  __typename
  drupalId
  langcode
  title
  articleReference {
    ... on ContentArticle {
      drupalId
      langcode
      title
    }
  }
}

After generate, the initial file will be set back to the original version with __typename replaced by __typename:_original_typename.

Development

To manually test on sample fragments.

pnpm ./cli.cjs generate --path ./tests/fragments