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

@gracious.tech/bible-references

v0.1.1

Published

Bible reference detection, parsing, and rendering that supports any language.

Downloads

55

Readme

Bible References

Bible reference detection, parsing, and rendering that supports any human language.

It's designed for use with fetch(bible) but can be used independently of it. See it in action via the fetch(bible) enhancer.


import {PassageReference, detect_references} from '@gracious.tech/bible-references'

// Simple args
const ref1 = new PassageReference('jhn', 3, 16)

// Complex args
const ref2 = new PassageReference({
    book: 'jhn',
    start_chapter: 3,
    start_verse: 16,
    end_chapter: 3,
    end_verse: 17,
})

// Parse string
const ref3 = PassageReference.from_string("John 3:16-17")

// i18n
const ref4 = PassageReference.from_string("Giăng 3.16-17", {jhn: "Giăng"})

// Convert to string
const ref1_str = `See ${ref1}`  // See John 3:16
const ref4_str = ref4.toString({jhn: "Giăng"}, '.')  // "Giăng 3.16-17"

// Detecting references in a block of text
for (const match of detect_references("Multiple refs like Gen 2:3 or John 3:16 and Matt 10:8")){
    console.log(match.text)  // "Gen 2:3", "John 3:16", "Matt 10:8"
}

// Detection can be configured to suit different languages
const exclude_book_names = []  // E.g. To prevent "so 1 is" matching as "Song of Songs 1" add "so"
const min_chars = 1  // Default is 2 but Chinese can abbreviate books down to a single character
const match_from_start = false  // Default is true but Chinese can abbreviate using a middle char
detect_references("伯5:14", {job: "約伯記"}, exclude_book_names, min_chars, match_from_start)

Bible book codes are the same as USX but lowercase.

See your editor's auto-suggestions or the source code for the variety of methods available for inspecting and manipulating references. The fetch(bible) client will automatically supply the names of books from existing translations so that you don't have to. See methods:

  • BibleCollection.detect_references(text, translation_id)
  • BibleCollection.string_to_reference(string, translation_id)
  • BibleCollection.reference_to_string(ref, translation_id)