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

@frctl/react

v0.3.7

Published

React template adapter for Fractal.

Downloads

29

Readme

React template adapter for Fractal.

An adapter to let you use React templates with Fractal. Not supported for docs.

Installation

npm install @frctl/react --save-dev

Usage

Require the adapter in your Fractal configuration file:

// Require the adapter factory:
const createReactAdapter = require('@frctl/react');
// Create the adapter instance:
const reactAdapter = createReactAdapter({/* options */});
// Register the adapter as engine:
fractal.components.engine(reactAdapter);

PathProvider

The adapter exposes a React Context Provider component called PathProvider to allow usage of relative paths in static HTML exports. The rendered components and preview layouts are automatically wrapped with it.

const { PathProvider, PathContext, usePath } = require('@frctl/react/components');

const Button = (props) => {
  // use via useContext hook
  const path = React.useContext(PathContext);
  // use via provided hook
  const hookPath = usePath();

  return (
    <>
      {path.get('/path/to/asset.png')}
      {hookPath.get('/path/to/asset.png')}
      {/* use via consumer component */}
      <PathContext.Consumer>
        {(consumerPath) => consumerPath.get('/path/to/asset.png')}
      </PathContext.Consumer>
    </>
  )
};

Client-side rendering

This adapter only handles server-side rendering of the components. If client-side hydration/rendering is needed, this build pipeline has to be setup outside of Fractal.

The adapter sets _adapter.componentName prop in preview layouts that corresponds to the rendered component name and can be used to hydrate the markup client-side.

Options

renderMethod

Specify which method to use for rendering your components. Note that preview layouts are always rendered with renderToStaticMarkup.

const reactAdapter = createReactAdapter({
  // default is 'renderToString'
  renderMethod: 'renderToStaticMarkup',
});

ssr

Enable/disable server side rendering of components.

const reactAdapter = createReactAdapter({
  // default is true
  ssr: false,
});

You can force server-side rendering on specific components by setting meta.ssr to true in your component config. This will override the setting only for this component.

// icon.config.js
module.exports = {
  meta: {
    ssr: true,
  }
}

wrapperElements

By default the render method renders only the component exported in the component template file.

Sometimes it is necessary to wrap the rendered component, for example with a React Context provider.

Note you need to do the same wrapping when hydrating the component client-side.

const SomeComponent = require('some-react-component');
const reactAdapter = createReactAdapter({
  // default is []
  wrapperElements: [
    {
      component: SomeComponent,
      props: {
        some: 'prop',
        yin: 'yang',
      },
    },
    {
      component: '@fractal-component',
      props: {
        some: 'prop',
        yin: 'yang',
      },
    },
  ],
});

babelOptions

Override babel configuration, for example, to use TypeScript components. Babel is used for parsing component templates.

const SomeComponent = require('some-react-component');
const reactAdapter = createReactAdapter({
  // default is { presets: ['@babel/preset-react', '@babel/preset-env'] }
  babelOptions: {
    presets: ['@babel/preset-react', '@babel/preset-env', '@babel/preset-typescript'],
    extensions: ['.js', '.jsx', '.ts', '.tsx'],
  },
});