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

gatsby-bucklescript-output-linker

v0.0.3

Published

Plugin that makes Gatsby aware of GraphQL queries on your ReasonML codebase when it lives outside the src directory.

Downloads

8

Readme

gatsby-bucklescript-output-linker

Plugin that makes Gatsby aware of GraphQL queries on your ReasonML codebase when it lives outside the src directory.

Why

With the current solutions that allow you to use Gatsby with ReasonML and Bucklescript, you are not allowed to write your GraphQL queries in your ReasonML code, unless your .re, as well as their compiled versions .bs.js files sit right next to your Gatsby .js files, in the src directory. The reason for this is Gatsby currently only looks for query in the src, .cache, fragments and the folders of the Gatsby plugins that you've declared on your package.json.

There's nothing wrong with using the src directory for the codebases of both languages and your GraphQL queries should work just fine if you do. However, if you prefer to keep them in separate folders of you'd like Bucklescript build files not to live next to their sources, but to use Bucklescript's lib output folder, there isn't an easy way.

This plugin basically hacks a symbolic link between the Buckescript's lib output folder and this plugin's own directory in node_modules, that Gatsby will properly watch for changes and compile.

Setup

  1. Install gatsby-bucklescript-output-linker

    npm i gatsby-bucklescript-output-linker

    or

    yarn add gatsby-bucklescript-output-linker
  2. Add 'gatsby-bucklescript-output-linker' to gatsby-config.js.

    // gatsby-config.js
    module.exports = {
        // ...
        plugins: ['gatsby-bucklescript-output-linker']
        // ...
    };
  3. Your bsconfig.json file should have in-source disabled, to use lib as the output folder:

    {
        "name": "my-gatsby-app",
        "reason": { "react-jsx": 3 },
        "bs-dependencies": ["reason-react"],
        "sources": {
            "dir": "re",
            "subdirs": true
        },
        "package-specs": {
            "module": "es6",
            "in-source": false
        },
        "suffix": ".js",
        "refmt": 3
    }

    For more configuration options refer to the BuckleScript docs or the bsconfig.json spec

  4. That's it! Run your app just like you would and you should be able to write GraphQL queries in your .re files now.

Usage

Query Example in ReasonML

[@bs.module "gatsby"]
external useStaticQuery: string => Js.t(unit) = "useStaticQuery";

let backgroundImageQuery = [%raw
  {|graphql`
    query {
      site {
        siteMetadata {
          title
        }
      }
    }
  `|}
];

[@react.component]
let make = () => {
  let result = useStaticQuery(backgroundImageQuery);
  Js.log(result);
  React.null
};

License

MIT