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

@enonic/react-components

v5.0.1

Published

Library of React components for handling Enonic XP data and page components

Downloads

1,533

Readme

Enonic React Components

Library of React components for handling Enonic XP data.

Install

npm install --save @enonic/react-components

RichText

Here is an example using the RichText component to render RichTextData in a React component named MyComponent.

Typically the RichTextData would be fetched from Enonic XP via the Guillotine GraphQL API.

import type {
  ImageComponent,
  LinkComponent,
  MacroComponent,
  RichTextData
} from '@enonic/react-components';
import {RichText} from '@enonic/react-components';

interface RestProps {
  myCustomProp: string
}

const Image: ImageComponent = ({
  alt,
  sizes,
  src,
  srcSet,
  style,
}) => {
  return <img
    alt={alt}
    sizes={sizes}
    src={src}
    srcSet={srcSet}
    style={style}
  />;
}

const Link: LinkComponent = ({
  // children, // in aProps
    content: _content,
    media: _media,
    // href, // in aProps
    // target, // in aProps
    // title, // in aProps
    uri: _uri,
    ...aProps
}) => {
    return <a {...aProps} />;
}

const HelloWorldMacro = ({
  config,
    children,
  myCustomProp
}: {
  config: Record<string,any>
  myCustomProp: RestProps['myCustomProp']
}) => {
  return (
      <>
          <h1>Hello, World! < /h1>
    {
        children
    }
    </>
  );
}

const Macro: MacroComponent<RestProps> = ({
  config,
  descriptor,
    children,
  ...rest
}) => {
  if (descriptor === 'com.enonic.app.example:helloworld') {
    const props = {...rest, config};
      return <HelloWorldMacro {...props} > {children} < /HelloWorldMacro>;
  }
  throw new Error(`Macro not found: ${descriptor}`);
}

export function MyComponent({data}: {data: RichTextData}) {
  return (
    <RichText<RestProps>
      className='someclass'
      data={data}
      Image={Image}
      Link={Link}
      Macro={Macro}
      tag='mytag'
      myCustomProp='lorum ipsum'
    />
  );
}

Regions

The Regions, Region, Layout, Page and ComponentTag components, are typically used with React4xp.

Here is an example using the Regions component:

Page controller

import { getContent } from '/lib/xp/portal';
import { render } from '/lib/enonic/react4xp';

export function get(request) {
  const content = getContent();
  const react4xpId = `react4xp_${content._id}`;
  return render(
    entry,
    props: {
      regionsData: content.page.regions,
      names: "main",
      tag: "main",
    },
    request, {
      body: `<!DOCTYPE html><html lang="en">
  <head>
    <meta charset="UTF-8">
    <title>${content.displayName}</title>
  </head>
  <body>
    <div id="${react4xpId}"></div>
  </body>
</html>`,
      id: react4xpId,
    }
  );
}

React4XP Entry

import React from 'react';
import { Regions } from '@enonic/react-components';

function Page (props) {
  return (
    <div>
      <Regions {...props} />
    </div>
  );
}

export default (props) => <Page {...props}/>;