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

@chili-publish/studio-connectors

v1.18.0

Published

[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://github.com/chili-publish/grafx-connector-template/blob/main/LICENSE)

Downloads

285

Readme

GraFx Studio Connectors

License: MIT

GraFx Studio Connectors is an innovative concept that enables seamless integration with any third-party application capable of serving Studio-compliant resources. We aim to provide a solution that is simple to explain, easy to develop, and maintainable.

🌐 General Connector Concept

Our high-level technical goals for the Studio Connectors are:

  • Written in popular and easily understood scripting languages (TS, JS).
  • Capable of running connector logic in both client (browser) and server contexts.
  • Secure and isolated from the browser.
  • Enforces memory and CPU limits to ensure an optimal user experience.
  • Small footprint with high performance.

📐 Schematic

Connector Architecture Overview

🔒 Authentication

We've decoupled authentication and authorization from the connector. You should not store application secrets or anything that allows malicious use of the API you want to connect to inside the connector code. We support several basic authentication methods:

  • HTTP Header
  • OAuth2 Client Credentials
  • OAuth2 Resource Owner Password Credentials

You can choose an authentication method for both client (browser) and server side individually. We provide the tools for secure implementation, but the end responsibility lies with the connector author.

QuickJs

We use QuickJS to execute all user-provided scripts, which acts as a Virtual Machine, ensuring the script can never access anything outside the VM. This allows us to restrict the available APIs to the connector developers, ensuring the connector code can safely run both on client (browser) and server (during output generation).

Connector.js

This repository contains examples of Typescript connectors that can be transpiled to a Javascript module. The current connector API is in version 1.0 and is the minimal APIs needed for a full-featured Media browser and things like Dynamic Asset Providers. We need your feedback! If you think you're missing critical stuff to implement your connector, let us know! Feel free to open a ticket on the SDK repo.

Connector.json

This is the wrapper adding metadata to the connector script. This Json can be uploadded using the experimental Connector endpoints of the Environment API. Reach out to your Customer Success contacts to help you set this up. Later this year we will provide a UI to manage connectors on the GraFx platform.

📚 SDK Documentation

Check out the official SDK documentation on GitHub

📬 Feedback?

We'd love to hear from you! If you have any technical feedback, feature requests, bugs to report, or general technical questions, don’t hesitate to create a new issue in the SDK repository.

📄 License

This project is MIT licensed.