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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@liquisio/git-cli

v0.0.17

Published

Tool to connect Blocks Code to Github - [re]connect local code to remote with smart conflict detection

Readme

LQ CLI

Git reconnect tool for Wix Blocks. When your container resets and .git disappears, run one command to reconnect.

Beta Version

Looking for beta testers or any feedback. Please read this doc carefully before you start. Report issues or ask questions here

Quick Start

1. Install (paste in Wix Blocks terminal):

cd /user-code && npm install @liquisio/git-cli --cache=/tmp/.npm && export PATH="$PATH:./node_modules/.bin"

Paste tip: Use Ctrl+Shift+V (Windows/Linux) or Cmd+Shift+V (Mac)

2. Create config at src/backend/lqcli.config.mjs:

export default {
  git: {
    name: 'Your Name',
    email: '[email protected]',
    user: 'github-username',
    repo: 'repo-name',
  },
};

3. Create token at src/backend/.env:

LQCLI_TOKEN=github_pat_xxxx

Get a token at github.com/settings/personal-access-tokens with Contents: Read and write permission.

4. Push or Pull your code:

lqcli push     # Push local code to GitHub
lqcli pull     # Pull GitHub code to local
lqcli status   # Compare local vs remote (read-only)

Done. Your .git is restored — use normal git commands until the next reset.

Before You Start

Backup your code before testing:

Option 1: Duplicate your Blocks app Test on the copy

Option 2: Download a backup Tar your src folder and download the file

tar -czvf /user-code/backup.tar.gz src/

Then right-click backup.tar.gz in the VS Code file explorer → Download

Notes

  • If you loose any files, there is no going back.
  • The cli installation, status and push commands are safe as they do not touch your source code.
  • Pull command is tricky, its a bit complex so lets take measures till we get to Version 1.
  • I have about 350 tests which are doing a good job and I have now been using this tool for 2 weeks.
  • Extra tip : I write minimal code in Widget's main source files and skip the src/site directory completely using skipDirectories: ['site'] setting in config file.

Commands

| Command | Description | |---------|-------------| | lqcli push | Push local code to GitHub | | lqcli pull | Pull GitHub code to local | | lqcli status | Compare local vs remote | | lqcli restore | Restore from backup |

After Reconnection

Once you run lqcli push or lqcli pull, your .git is restored. Use standard git commands for the rest of your session:

git status                      # Check changes
git add . && git commit -m "x"  # Commit
git push                        # Push to GitHub
git log                         # View history

lqcli is only needed again when your container resets and .git disappears.

Limitations

Note: These limitations apply to lqcli only. After reconnection, all standard git commands work normally.

  • Single branch — Works with one branch (default: main)
  • GitHub only — No GitLab, Bitbucket, or self-hosted support
  • Single directory sync — Only syncs src/ (configurable)
  • No merge — Uses reset/overwrite, not git merge
  • All-or-nothing conflicts--ours/--theirs applies to all files
  • Ephemeral backups — Stored in /tmp, lost on reboot

See full documentation for all options and details.