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

@arc-fusion/content-integrations

v1.2.0

Published

Downloads

138

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

joan.acostajoan.acostajakmajakmastevethedevstevethedevfernangpefernangpefloatswitchfloatswitchpreyes89preyes89barnettrbarnettrstemlemstemlemjsatriajsatriauncompileduncompiledsbankssbanksshk172shk172beltrancalizbeltrancaliz

Keywords

Readme

PageBuilder Content Integrations

Install npm libraries

In pb-admin root folder run npm install --legacy-peer-deps

Static integrations build

Option 1: build within the integrations folder: In packages/content-integrations/ folder run npm run build

Option 2: Build within the pb-admin root: In pb-admin/ run npm run build:integrations

Real time build

In packages/content-integrations run npm run build:watch

Shared components and utilities

These live in the packages/content-integrations/shared/ and consist of the following types of items:

  • components - React components such as checkboxes, selects, etc.
  • icons- JSX written SVG icons
  • modules - Generic JS functions that can be used across integrations
  • services - API calls

Creating new integrations

  • Create new folder within packages/content-integrations/src/ folder
  • Code in here should follow standard ARCXP coding guidelines and practices as a component.

Local development

In a separate terminal go to the folder: packages/content-integrations and run npm run build:watch. This will build the content-integrations package when a change is made in it's structure.

Note: If something doesn't update correctly, delete the folder: packages/content-integrations/dist. Rerun the static build step from above to re-create the dist folder. Alternatively you could also run npm run clean within the packages/content-integrations folder. You may need to restart your pb-admin front end to have it re-detect file changes since the dist folder is what it was aware of.

Publishing your changes

Once you've finished work on your integration and the branch is ready for merging, you will need to update the packages/content-integrations/package.json version number and run an npm publish in that folder to deploy the updated package.

Note: If you have issues publishing, please reach out to the team and someone can help get you set up for this action.

Next, bump the version listed in the pb-admin root package.json to match your newly deployed version and run npm install --legacy-peer-deps to pull it in.