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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@basaldev/blocks-frontend-framework

v5.1.0

Published

<p align="center"><img width="200px" src="docs/logo.png" /></p> <h1 align="center" >blocks-frontend-framework</h1> <p align="center">❤️</p>

Readme


What is this?

The Nodeblocks Framework is a library which provides scaffolding for building Nodeblocks frontend React applications. Using this framework, you can quickly build a frontend application made up of multiple Nodeblocks blocks, composed together using a standardized architecture.

🏗 Project Structure

.
├── .github
├── .husky                 # husky settings - @basaldev/lint-staged-config
├── .vscode                # vscode settings
├── .yarn                  # yarn binary, config and project dependencies
├── coverage *             # jest coverage report
├── dist *
├── docs
├── public                 # files that will be exported to npm (e.g. svg and other images)
├── src
│   ├── design-system      # Design system components
│   │   ├── basic
│   │   ├── composite
│   ├── examples           # Example applications (used for testing locally)
│   ├── framework
│   │   ├── app
│   │   ├── block
│   │   ├── template
│   │   └── types.ts
│   └── index.ts
├── .eslintignore
├── .eslintrc.js            # @basaldev/eslint-config
├── .gitignore
├── .nvmrc
├── .pnp.cjs                # yarn config
├── .pnp.loader.mjs         # yarn config
├── .prettierignore
├── .prettierrc.json        # @basaldev/prettier-config
├── .yarnrc.yml             # yarn config
├── cspell.config.js        # @basaldev/cspell-config
├── .yarnrc.yml             # yarn config
├── index.html              # Example application index.html
├── package.json
├── README.md
├── tsconfig.json           # @basaldev/tsconfig
├── vite.config.ts          # Vite configuration for building and running the project
└── yarn.lock

🔰 Starting a new project using frontend-framework

  1. Create a new repository on github
  2. Create a new vite project using the react-ts template. See here for instructions.
  3. Import the npm package @basaldev/blocks-frontend-framework into your project
  4. Copy one of the appropriate examples from src/examples into your project root (Note that you will need to copy examples/core-styles.css as well to configure the base styles for the application)
  5. TODO: Add instructions for importing the application

Customizing CSS and themes

The framework uses CSS modules to scope styles to each component, as well as CSS variables that can be used to configure the framework.

🔰 Contributing Setup

Create a Github Personal Auth Token

  1. Go to Github Developer Settings > Personal Tokens > Generate new token
  2. Click 'Generate Token'
  3. Input a name for your token.
  4. Select repo checkbox
  5. Select write:packages
  6. Add to your local environment - .zshrc .bashrc etc
export NODEBLOCKS_DEV_TOKEN=__INSERT_YOUR_TOKEN_HERE__

Install NVM

Install Yarn (Global)

Yarn must be installed globally for the project's NodeJS version. This should be done so using the command below.

nvm use && npm install -g yarn

Install Husky 🐺

yarn dlx husky init

⚠️ IMPORTANT: Only use the yarn command install or run scripts. Do not use npm run xxx

🪄 Usage

Run vite

First, create a .env file in the root of the project:

cp .env.example .env

Fill this .env file with the appropriate URLs for the backend services.

Second, create a local https cert

brew install mkcert
mkcert -install
mkcert localhost

Then, run the following command to start the vite server

yarn dev

By default, the vite server will use the hello-world example. To use a different example, run the following command:

APP_TYPE=example-folder yarn dev

(Generally, instead of this, you will want to yarn link a separate project that uses the framework.)

Run storybook

yarn storybook

Run unit tests

yarn test

Installing packages

yarn add <package> | yarn add <package> -D

Linking local packages for local testing

To add blocks-frontend-sdk, run this yarn command first:

yarn link /full/absolute/path/to/blocks-frontend-sdk

Then, add this to vite.config.ts:

export default defineConfig({
  ...
  optimizeDeps: {
    include: ['@basaldev/blocks-frontend-sdk'],
  },
  ...
});

⚡️ Special Notes for VSCode Users

📐 Required Extensions

Please ensure the following extensions are installed:

  • arcanis.vscode-zipfs
  • dbaeumer.vscode-eslint
  • seatonjiang.gitmoji-vscode
  • henrynguyen5-vsc.vsc-nvm (optional)

🛠 Workspaces

The kit uses vscode workspaces for vscode project settings:

  • All common vscode project settings should be specified in the .vscode/${project_name}-workspace file.
  • Personal user settings should be added to .vscode/settings.json (gitignored)
  • ⚠️ You must open this project as a workspace in vscode This can be done by clicking the workspace file while in vscode, or by using File > Open workspace from file.

🪛 TypeScript

When prompted asking which typescript VSCode should use, it's very important that you choose the local project version located at .yarn/sdks/typescript/...

💅 Prettier

If you have the prettier extension installed, please disable it for this project. ts-kit uses eslint to execute prettier, so having prettier enabled in vscode will cause conflicts and strange behavior.

🤖 Format on Save (optional)

Add the following code to your .vscode/settings.json will automatically fix all eslint errors whenever you save a file.

  "editor.codeActionsOnSave": {
    "source.fixAll.eslint": true
  }

🚀 Package Deployment

This library uses github registry to publish private npm package. For detailed instructions see here

💡 Note: that npm is used for version & publish commands

1. Bump version

npm version ${VERSION}

2. Build Package

yarn build

3. Publish Package

npm publish

Then go to github https://github.com/basaldev/blocks-frontend-sdk/packages to check published packages.