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

@bibletags/bibletags-widget

v0.1.4

Published

## About

Vulnerabilities

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

Links

Git

Maintainers

andyhubertandyhubert

Keywords

Readme

Bible Tags

About

Original language Bible study for everyone, in every language.

Vision: That every Christian might have free access to the Bible tagged to the original Hebrew, Aramaic and Greek with parsing and lexical information—all in their own language.

For more information on this project, see the Bible Tags website.

Repos

Bugs

Bible Tags Widget

IMPORTANT NOTE: This aspect of the Bible Tags project has been placed on hold while focus is given to the React Native app. More on project phases.

Basic information

  • Built with create-react-app
  • Deploys to static files
  • Lives on a cdn
  • Sends graphql queries and mutations to bibletags-data

Development

This project has been set up in such a way as to allow you to work one of the repositories without the need of cloning and running the others locally.

But, of course, you can run more than one locally at a time when need be. To do so, simply change the widget and data query parameters appropriately. Valid values are local, staging and production (default).

Note: A lot of data is cached in the browser so as to make this widget fast and offline. Thus, in testing, you may need to delete application storage (i.e. localStorage, etc) from your browser from time to time.

bibletags-data (backend)

Installation

Follow the instructions found here.

bibletags-widget

Installation

git clone https://github.com/educational-resources-and-services/bibletags-widget
cd bibletags-widget
npm install

Running

  • npm run dev (to start the widget and open test.html in your browser)

Note: The widget will automatically hot-reload with each change you make.

bibletags-widget-script

Installation

git clone https://github.com/educational-resources-and-services/bibletags-widget-script
cd bibletags-widget-script
npm install

Running

  • npm run open (to open test.html in your browser)

Note: You will need to refresh the browser page with each change.

To test a deployed build, add the appropriate value to either the widgetScriptBuild or widgetScriptTestBuild query parameter.

Updates To Embed

  • Rarely, when widget-script.js requires updating, embedding sites/apps must make this update manually. On this occasion there will likely also be breaking changes in the API. Such changes will be annotated here.