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 🙏

© 2026 – Pkg Stats / Ryan Hefner

gatsby-plugin-nebo

v0.1.3

Published

Builds embeddable components from https://nebohq.com

Readme

gastby-plugin-nebo

A Gatsby plugin that sources data from Nebo, the visual React builder.

This plugin builds the pages you created in Nebo.

Table of Contents

Install

  1. Sign up for Nebo. After you've signed in, navigate to "Settings" on the side bar.

  2. Install gatsby-plugin-nebo:

# if you are using npm and package-lock.json
npm install gatsby-plugin-nebo
# if you are using yarn and yarn.lock
yarn add gatsby-plugin-nebo
  1. Find and copy the access token. You can find it in the "Developers" section:
  1. Run the following command:
# with npm
npx nebo init --access-token=your-access-token

# with yarn
yarn run nebo init --access-token=your-access-token
  1. Add your plugin configuration to gatsby-config.js. It should look something like this:
{
  "resolve": "gatsby-plugin-nebo",
  "options": {
    "accessToken": "[YOUR ACCESS TOKEN]",
    "pageTemplatePath": "./NeboPage.jsx"
  }
}
  1. This will generate three files: nebo.config.js, nebo.js, and NeboPage.jsx. We'll use the first to import components, the second output Nebo assets for use in settings, and the third is the layout of pages coming from Nebo.

  2. You're now ready to build pages in Nebo!

Installing the plugin generates the configuration (./src/config/nebo-config.js) and the page template (./src/templates/nebo-page.js). If you have filled in your access token in gatsby-config.js, it will automatically be added to the configuration.

How to use

Adding pages

  1. Navigate to your Nebo home page.
  2. Click "New Page".
  1. Once you're in the editor, click on the gear icon in the top right to go to page settings.
  1. Here, you can change the name and slug of your page. The slug will be part of the url of the page in the format: [YOUR_DOMAIN]/[SLUG]. For example, for the slug hello_world will create a page at https://nebohq.com/hello_world.
  2. Now, click on the top component on the right. If you named your page Hello, world!, it will be called Hello, world!.
  1. Here you, can edit the page in any way you want. For the sake of this example, we added "This is a test page!" as the content of this page. You can find more information on how to use the editor here.
  2. Save your work by clicking the cloud button on the top right.
  3. Once you reload your development server (npm run develop) or redeploy, the page will now be available in your Gatsby app.

Adding your styles

  1. Go to nebo.config.js.

  2. Change the globalStylesPath option to point to your global styles.

module.exports = {
  // other options
  globalStylesPath: ["./src/stylesheets/application.scss", "./src/stylesheets/globals.css"],
};
  1. Run the following command to compile your Nebo assets. This will build two files nebo.css and nebo.js. It will also keep track as you change files.
# with npm
npx nebo watch

# with yarn
yarn run nebo watch
  1. On the Nebo website, navigate to "Developer" settings in the Nebo App. Add [YOUR_DEVELOPMENT_URL]/nebo.css (usually something like localhost:3000/nebo.css) to "CSS Source URL".

  2. Your styles have now been imported! You should see them after refreshing the Nebo editor.

  3. Before you commit your changes, please run the following commands. These will compile the Nebo assets for production.

# with npm
npx nebo

# with yarn
yarn run nebo
  1. After you've deployed your changes, navigate to "Developer" settings in the Nebo App. Switch the "CSS Source URL" to the path of your production Nebo asset (usually [YOUR_PRODUCTION_URL]/nebo.css).

Adding your component library

  1. Run the following command to compile your Nebo assets. This will build two files nebo.css and nebo.js. It will also keep track as you change files.
# with npm
npx nebo watch

# with yarn
yarn run nebo watch
  1. Navigate to nebo.js. Add one of your components to the Nebo directory in the indicated place.
import React from 'react';
import ReactDOM from 'react-dom';
import Component, { configure, fetchComponent } from '@nebohq/nebo';

const accessToken = '[ACCESS_TOKEN]';
const directory = configure({
  directory: {
    // Add your components here
  },
  react: React,
  renderer: ReactDOM,
  accessToken,
});

const fetchSchema = async (idOrSlug) => fetchComponent({ idOrSlug, accessToken });

const NeboComponent = Component;
export default NeboComponent;
export { directory, fetchSchema };
  1. On the Nebo website, navigate to "Developer" settings in the Nebo App. Add [YOUR_DEVELOPMENT_URL]/nebo.js (usually something like localhost:3000/nebo.js) to "Javascript Source URL".

  2. Your component component has now been imported! You should see it in the library dropdown under "Imported Components".

  3. Before you commit your changes, please run the following commands. These will compile the Nebo assets for production.

# with npm
npx nebo

# with yarn
yarn run nebo
  1. After you've deployed your changes, navigate to "Developer" settings in the Nebo App. Switch the "JavaScript Source URL" to the path of your production Nebo asset (usually [YOUR_PRODUCTION_URL]/nebo.js).

Configuration Options

module.exports = {
  plugins: [
    ...otherPlugins,
    {
      resolve: 'gatsby-plugin-nebo',
      options: { 
        accessToken: '[ACCESS_KEY]',
        pageTemplatePath: `${__dirname}/NeboPage.jsx`, // path to the page template
        ignoredPageSlugs: [] // list of page slugs you want to ignore
      },
    },
  ],
};
  • accessToken - [required] - used to access your components from your Gatsby app.
  • pageTemplatePath - path to the Nebo page template. This controls the look of your pages.
  • ignoredPageSlugs - list of pages to ignore, by their Nebo slug.

Questions and feedback

If you have questions about Nebo or want to provide us feedback, join our discord!