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

@constellation4sitecore/enhancers

v22.2.9

Published

A collection of XM Cloud compatible libraries for SXA Sitecore Development.

Downloads

1,751

Readme

Constellation Enhancers

Installation

npm install @constellation4sitecore/enhancers --save

Usage

With DatasourceRendering

Similarly to withDatasourceCheck that comes OOTB to enforce a component to have a Datasource, we created a new High-Order component called withDatasourceRendering that is meant to help developers code faster by automatically checking for a Datasource if available, if not the datasource will fallback to the context item.

import { withDatasourceRendering } from '@constellation4sitecore/enhancers';

export default withDatasourceRendering()<HomepageMastheadProps>(HomepageMasthead);

This pattern takes the Component and validates if the rendering has any datasource to return fields as normal call otherwise fields will be populated with useSitecoreContext

Get Rendering Index

This helper function allows you to get index of the rendering.

const placeholders = layoutData.sitecore?.route?.placeholders;
const result = getRenderingIndex(placeholders, rendering.uid as string, 'TabbedContentRowTab');

Inputs:

  • placeholders: all layout placeholders
  • UID: Rendering UID
  • Component Name: Name of the child component.

Filter Placeholders

For example if you want to build a Tab Content Row component, you will facing an issue, if you don't filter placeholders in experience editor it will trought an error to avoid this filterPlaceholders will filter just components that name are not equal to "code".

export const getStaticProps = async (rendering: ComponentRendering) => {
  const newTabs = [] as TabViewModel[];
  const tabContentRows = filterPlaceholders(
    (rendering.placeholders as unknown as TabbedPlaceholders).TabbedContentRowTabs
  );
  for (const tabContentRow of tabContentRows) {
  }
};

Modify Children Properties when using Placeholders

For example you want to send properties to a child component that is inserted into a Placeholder.

const MyComponent = ({ fields, params, rendering }: MyComponentProps) => {
  useModifyChildrenProps(rendering, {
    myProp1: fields.myProp1,
    myProp2: 'hello world!',
  });

  return (
    <Placeholder
      name={`my-chindren-modules-${params.DynamicPlaceholderId}`}
      rendering={rendering}
    />
  );
};

Note: This serves as a workaround in cases where modifyComponentProps prop in the Placeholder Component fails to function properly. This issue arises due to the component-props.ts plugin overriding the props through the getStaticProps method.