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

@ossy/cms-client-react

v0.0.74

Published

React bindings for cms rest api

Downloads

158

Readme

React bindings

To make it as easy as possible to use our cms we have created a library with react hooks you can use to fetch data.

Getting started

To use these hooks install the package @ossy/cms-client-react

npm install @ossy/cms-client-react

Then we simply need to wrap our app in a that will handle data storage and configuration for us. You will need the workspaceId for the workspace you want to fetch data from. The workspaceId can be found in the list of workspaces you have access to or in the url when you view the resources in the UI.

// App.jsx
import { WorkspaceProvider } from '@ossy/cms-client-react'
import { MyComponent } from './MyComponent.jsx'

export const App = () => (
  <WorkspaceProvider workspaceId="your-workspace-id">
    <MyComponent />
  </WorkspaceProvider>
)
// MyComponent.jsx
import { useResources } from '@ossy/cms-client-react'

export const MyComponent = () => {
  const { status, resources } = useResources('/folder/path/in/cms')

  return (
    <>
      { status === 'Error' && (
        <>Something went wrong</>
      )}

      { status === 'Loading' && (
        <>Loading...</>
      )}

      { status === 'Success' && (
        resources.map(resource => (
          <div key={resource.id}>
            {resource.name}
          </div>
        ))
      )}
    </>  
  )
}

Reference

useResources

const { status, resources } = useResources('/')

Parameters

  • path - Folder path in the cms UI

Returns

Returns an object containing

  • status - String value that indicates loading status. Can be used to show loading indicators or error screens. Possible values are: NotInitialized, Loading, Success, Error
  • resources - Array of resources, defaults to an empty array when loading is not Success

useResource

const { status, resource } = useResource('resourceId')

Parameters

  • resourceId - Id of the resource you want to fetch

Returns

Returns an object containing

  • status - String value that indicates loading status. Can be used to show loading indicators or error screens. Possible values are: NotInitialized, Loading, Success, Error
  • resource - The fetched resource, defaults to an empty object when status is not Success