Obsidian only loads built plugin files. After every update:
# in repo
npm install
npm run build
# copy built artifacts into your vault
cp manifest.json main.js styles.css /path/to/vault/.obsidian/plugins/obsidian-biblehub-lexicon-importer/git pullnpm run build- Copy manifest.json, main.js, styles.css into your vault’s plugin folder
Tip: for development, you can symlink the plugin folder to the repo and use
npm run devif you prefer.
Import BibleHub Strong's lexicon entries into graph-ready Obsidian notes with typed links, YAML frontmatter, and optional BFS crawling.
- Accepts Strong's IDs (e.g.,
G2222,H1623) or BibleHub URLs. - Fetches Strong's pages with rate limiting and caching.
- Parses lexical fields and basic "See ####" cross-references.
- Writes notes with consistent YAML and section markers for future updates.
- BFS crawl of typed edges with depth/node limits.
- Copy this folder into your vault at
.obsidian/plugins/obsidian-biblehub-lexicon-importer. - In Obsidian: Settings -> Community plugins -> Enable "BibleHub Lexicon Importer".
- Open the command palette.
- Run:
Import Strong's as graph (BibleHub). - Enter a Strong's ID or a BibleHub Strong's URL.
Input examples:
G2222H1623https://biblehub.com/strongs/greek/2222.htmhttps://biblehub.com/strongs/hebrew/1623.htm
The plugin creates or updates notes under the configured root folder.
All settings are available in the plugin's settings tab:
- Root folder: destination for notes.
- Max depth: BFS crawl depth.
- Max nodes: maximum notes created/updated per run.
- Rate limit (ms): delay between requests.
- Skip existing notes: do not refetch/overwrite existing notes.
- Rename note on update: keeps titles in sync when re-importing.
Each note includes:
- YAML frontmatter with Strong's metadata and source URLs.
- Section markers:
<!-- imported: section_key -->. - Outbound link groups: see also / related / topical.
# Install deps
npm install
# Dev build (watch)
npm run dev
# Production build
npm run build
# Type check
npm run typecheck
# Lint
npm run lint# Run all tests
npm test
# Watch mode
npm run test:watch
# Coverage
npm run test:coverage
# Run tests matching a name
npm run test:specific -- "normalize"- BibleHub has Terms of Use. Keep usage user-initiated and rate-limited.
- The parser is intentionally simple and extensible. Improve section parsing as needed.
MIT