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

@blateral/b.kit-modx

v2.7.1

Published

This package provides an interface to connect b.kit components with the MODX CMS. To do so it defines slices that can be imported and used inside e.g. in a react nextjs project.

Downloads

736

Readme

b.kit logo

b.kit MODX

This package provides an interface to connect b.kit components with the MODX CMS. To do so it defines slices that can be imported and used inside e.g. in a react nextjs project.

Our ModxCloud is based on ContentBlocks that create JSON-Data that then is consumed by our kit-server template, sliced into perfect data then used to render components from b.kit. We use a lot of Snippets to adjust data in the CMS so we have to slice less. Additionally, we use Chunks to capsule data.

How a Page is structured is typically set in Templates. Those Templates use Chunks and Snippets to form and structure the JSON data.

Local Testing

The bundled package can be tested locally with a npm package called Yalc. Yalc acts as very simple local repository for locally developed packages to share them across a local environment.

Workflow

Install yalc globally: yarn global add yalc.

Inside the library/package repository:

  1. Run yarn build to bundle the package.
  2. Run yalc push to push it to local global store (~/.yalc).

Inside a repository that consumes the package:

  1. To link local package run yalc add <repository-name> (e.g. yalc add @blateral/b.kit).
  2. Before committing to remote repository remove the local package links by running yalc remove <repository-name> or yalc remove --all.
  3. Use yarn --check-files to savely install the remote packages defined in package.json. In some repositories there is also a script yarn lookup that does the same.