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

@builder.io/plugin-commercejs

v0.0.3

Published

Connect your Commerce.js account and data to your Builder.io content!

Downloads

2

Readme

Builder.io Commerce.js plugin

Connect your Commerce.js account and data to your Builder.io content!

Installation

Go to builder.io/account/organization and press on @builder.io/plugin-commercejs in the list of plugins, then hit save, you'll be prompted for to enter your publicKey next.

Installation screenshot

You will now see six new field types (for model fields, symbol inputs, custom components fields), and custom targeting attributes that can be used in three different contexts:

Custom targeting

Custom targeting in Builder.io allow users to target content by a multitude of attributes, and in this plugin you'll be able to add specific content to Commerce.js products or categories, for this you'll need first to set the target attributes on the host site, either by setting the userAttributes if you're rendering client side:

builder.setUserAttributes({
  product: currentProduct.id,
});

Or by passing it as a query param to the content API call, or in graqhql query for e.g in Gatsby or nextjs.

  • Commerce.js product when used as a custom targeting type, will target contexts where the field is set to the product ID, you'll need to set the product ID on the host environment, using one of the methods above. Alternatively, if you want to target by product handle use the Commerce.js product handle type in your custom targeting attributes.

  • Commerce.js category can be used as custom targeting attribute to target specific category by ID, you'll need to set the category ID on the host environment, using one of the methods above. Alternatively, if you want to target by product handle use the Commerce.js category handle type in your custom targeting attributes.

Component model fields

Component models can be used to represent product or collection page templates for all or a specific set of products/collections, using one of the following fields, you'll make previewing the templates for any product or collection straight-forward:

  • Commerce.js Product Preview is to be used as a custom field on component models, this will allow you to have templated editing url on your component model relevant to the Commerce.js product being previewed, for example you can set the url in your model to: https://www.mystore.com/product/${previewProduct.handle}, add a custom field of type Commerce.js Product Preview to the model, now when you create a new entry, the handle will be added dynamically to the preview url based on the preview product, it is recommended to add a default value to the Commerce.js Product Preview custom field, so users will land at a specific product page when developing a template component.

  • Commerce.js Collection Preview is to be used as a custom field on component models, this will allow you to have templated editing url on your component model relevant to the Commerce.js collection being previewed, for example you can set the url in your model to: https://www.mystore.com/collection/${previewCollection.handle}, add a custom field of type Commerce.js Collection Preview, now when you create a new entry, the handle will be added dynamically to the preview url based on the preview product, it is recommended to add a default value to the Commerce.js Collection Preview custom field, so users will land at a specific collection page when developing a template component.

Symbol Inputs

Using the field types Commerce.js Product and Commerce.js Collection as inputs, the UIs will prompt to search for products and collections. When consumed by APIs, SDKs, or in the Builder.io UIs, the value will be resolved automatically the in the form of a Builder.io Request object

{
  "yourFieldName": {
    "@type": "@builder.io/core:Request",
    "request": {
      "url": "..."
    },
    "data": {
      // Response data from the API request, e.g.:
      "product": {
        /* ... */
      }
    }
  }
}

How to develop?

Install

git clone https://github.com/BuilderIO/builder.git
cd plugins/commercejs
npm install

Run

npm run start

Add the plugin in Builder.io

Go to builder.io/account/organization and add the localhost URL to the plugin from the plugin settings (http://localhost:1268/[email protected]/commercejs)

NOTE: Loading http:// content on an https:// website will give you a warning. Be sure to click the shield in the top right of your browser and choose "load unsafe scripts" to allow the http content on Builder's https site when devloping locally

Now as you develop you can restart Builder to see the latest version of your plugin.

To uninstall your plugin, just remove it in the plugins UI

Seeing the plugin in action

Try creating a custom model, component, or symbol using a Commerce.js field, and edit away!

Frameworks

Builder.io uses React and Material UI for the UI, and Emotion for styling.

Using these frameworks in Builder plugins ensures best possible experience and performance.