quran-meta
    Preparing search index...

    quran-meta

    Quran Meta

    Static Badge Static Badge

    GitHub License GitHub Repo stars GitHub package.json version

    NPM Version npms.io npms.io npms.io npms.io NPM Downloads

    NPM Type Definitions GitHub top language Quality Gate Status Static Badge

    GitHub repo size GitHub code size in bytes npm bundle size npm bundle size

    This project is to help with Quran related meta queries.

    Answering Questions like:

    • How many ayahs in given surah of Hafs Riwaya or Warsh or Qalun (getAyahCountinSurah)
    • What is the juz of given ayah (getAyahMeta)?
    • What is the next ayah after given ayah (nextAyah)?
    • Is given ayah
      • a sajdah ayah (getAyahMeta)?
      • beginnning of a page (isAyahPageFirst)?
      • beginnning of a juz (isAyahJuzFirst)?
    • Find
      • next or previous ayah (nextAyah/prevAyah)
      • juz findJuz and findJuzByAyahId
      • maqra/rub-el-hizb findRubAlHizb, getRubAlHizbMetaByAyahId
      • page findPage by surah/ayah
      • AyahId of a given surah/ayah (findAyahIdBySurah)
      • find range around ayah (findRangeAroundAyah)
    • Get meta data for
      • ayah (getAyahMeta)
      • surah (getSurahInfo, getSurahInfo)
      • page (getPageMeta)
      • juz (findJuzMetaBySurah)
      • maqra/rub-el-hizb (getRubAlHizbMeta, getRubAlHizbMetaByAyahId)
    • Validates ayah/surah id (checkValidAyahId,checkValidSurah, checkValidSurahAyah, etc)
    • Typescript type guards (isValidAyahId, isValidAyahNo, isValidSurah, isValidSurahAyah, isValidJuz, isValidHizb, isValidRubAlHizb, isValidPage)
    • converts [surah, ayah] to ayahId and vice-verse ( findSurahByAyahId and findAyahIdBySurah)
    • Checks and turns strings of type "x:y" or "x:y1-y2" to surah/ayah range (ayaStringSplitter).
    • Checks and parses strings of type "x" to Surah (surahStringParser).
    • Supports multiple riwayas (Hafs, Qalun, Warsh are ready. Douri, Shuba, Sousi are on the way) with riwaya-specific data and features.
    • Type-safe riwaya-specific methods (e.g., Qalun's Thumun al-Hizb).
    • Custom riwaya instances for advanced use cases. If you want to use quran-meta library with your own data (e.g another riwaya or different pagination than we support) just create your own instance of QuranRiwaya with your data.
    • Fully documented with examples.
    • 100% unit test covered with data correctness validation against multiple data sources.
    • Fully typed with Typescript types and type guards.
    • Zero dependencies, lightweight and fast.
    • Works in both browser and Node.js environments.
    • Compatible with modern JavaScript and TypeScript projects.
    • Supports modern module systems (ESM, CommonJS, IIFE).
    • Open source and community driven.
    • Easy to use API with both functional and class-based approaches.
    • Tree-shakeable riwaya-specific imports for optimal bundle size.
    • Supports various build systems and bundlers.
    • Comprehensive error handling and input validation.
    • Suitable for a wide range of Quran-related applications.
    • Modular and extensible architecture.
    • Clear and consistent naming conventions.
    • Rich set of utility functions for Quranic metadata.
    • Easy integration with other Quranic libraries and tools.
    • Actively maintained and updated.
    • Actively seeks community feedback and contributions.
    • Supports multiple mushaf page numbering systems (planned for future updates).
    • More riwayas and recitations (planned for future updates).
    • Enhanced performance optimizations (planned for future updates).
    • Additional utility functions (planned for future updates).
    • Community contributions and plugins (Submissions welcome).
    • Support for additional languages and locales .
    • Improved documentation and tutorials.
    • Interactive online tools and demos (please, submit in issues).
    • More data sources for cross-validation (please, suggest in discussions).
    • Integration with Quran text rendering libraries.
    • Collaboration with Quranic studies platforms.
    • Integration with Quranic search engines.
    • Advanced analytics and reporting features.
    • Community-driven feature requests and voting.

    See here for API documentation

    See in action and try it without installing anything:

    • Static Badge - interactive playground for Quran-Meta
    <script src="quran-meta.js"></script>

    Also modern browsers allow

    <script type="module">
    import quranMeta from "quran-meta.esm.js"
    </script>

    The library is available from various CDNs

    $ npm i --save quran-meta

    Tree-Shakeable Riwaya-Specific Imports (Recommended)

    For optimal bundle size, import from riwaya-specific entry points. This ensures only the data you need is bundled:

    // Hafs-specific import (only Hafs data bundled, ~50% smaller)
    import { getAyahMeta, findJuz, meta, quran } from "quran-meta/hafs"

    console.log(`Total ayahs: ${meta.numAyahs}`) // 6236

    // Using functional API (Hafs is default)
    const ayahMeta = getAyahMeta(1)
    console.log(ayahMeta.juz) // => 1

    // Using class API
    const next = quran.nextAyah(1, 7)
    console.log(next) // => [2, 1]

    // Qalun-specific import (only Qalun data bundled)
    import { getAyahMeta, findThumunAlHizb, meta, quran } from "quran-meta/qalun"

    console.log(`Total ayahs: ${meta.numAyahs}`) // 6214
    console.log(`Thumun al-Hizbs: ${meta.numThumunAlHizbs}`) // 480

    // Qalun-specific features available
    const thumun = findThumunAlHizb(1, 1)
    console.log(thumun) // => 1

    const ayahMeta = getAyahMeta(1)
    console.log(ayahMeta.thumunAlHizbId) // Available in Qalun!

    Benefits of riwaya-specific imports:

    • ✅ 50% smaller bundle - only loads the riwaya you need
    • ✅ Zero configuration - works immediately, no initialization required
    • ✅ Tree-shakeable - unused riwayas are eliminated by bundlers
    • ✅ Type-safe - full TypeScript support with correct types per riwaya
    • ✅ Future-proof - easily add new riwayas without breaking changes

    Class-Based API

    For generic code that works with multiple riwayas, use the class-based API:

    import { QuranRiwaya } from "quran-meta"

    // Create a Hafs instance
    const hafs = QuranRiwaya.hafs()

    // Get surah metadata
    const surahMeta = hafs.getSurahMeta(2)
    console.log(surahMeta.name) // => 'البَقَرَة'
    console.log(surahMeta.ayahCount) // => 286

    // Find juz information
    const juz = hafs.findJuz(2, 1)
    console.log(juz) // => 1

    // Check if ayah is first in juz
    const isFirst = hafs.isAyahJuzFirst(149)
    console.log(isFirst) // => 2

    // Get ayah metadata
    const ayahMeta = hafs.getAyahMeta(1)
    console.log(ayahMeta) // => { surah: 1, ayah: 1, juz: 1, page: 1, ... }

    // Navigation
    const next = hafs.nextAyah(1, 7)
    console.log(next) // => [2, 1]

    // Use Qalun riwaya for Thumun al-Hizb support
    const qalun = QuranRiwaya.qalun()
    const thumun = qalun.findThumunAlHizb(1, 1)
    console.log(thumun) // => 1

    // Create custom riwaya instance
    const custom = QuranRiwaya.create("Hafs")

    Benefits of the class-based API:

    • ✓ No repetitive riwaya parameter in every function call
    • ✓ Clear context with a dedicated instance
    • ✓ Better IDE autocomplete and type safety
    • ✓ Chainable and fluent API
    • ✓ Riwaya-specific methods (e.g., Qalun's Thumun al-Hizb)

    Legacy Functional API

    The original functional API is still available for backward compatibility:

    In Node.js see example here:

    var quranMeta = require("quran-meta")

    console.log(" Assalam Aleykum! ") // => 'Assalam Aleykum!'
    console.log(`There are ${quranMeta.meta.numSurahs} suras in the Holy Quran`) // => 'There are 114 suras in the Holy Quran'

    In the browser/ES:

    import { meta } from "quran-meta"
    console.log("Assalam Aleykum!")
    console.log(`There are ${meta.numSurahs} suras in the Holy Quran`) // => 'There are 114 suras in the Holy Quran'

    In TypeScript:

    import { meta, getAyahCountinSurah, AyahNo, Surah } from "quran-meta"

    console.log(`There are ${meta.numSurahs} suras in the Holy Quran`)

    for (let surah: Surah = 1; surah <= meta.numSurahs; surah++) {
      const ayaCount = getAyahCountinSurah(surah)
      console.log(surah, ': ',ayaCount)
    }

    Here's a paragraph describing this major feature:

    quran-meta now supports custom riwaya instances, allowing you to use the library with your own Quranic data sources. Whether you're working with a different recitation style (riwaya) not yet included in the library, using an alternative pagination system (like different mushaf layouts with 13, 15, or 16 lines per page), or integrating region-specific Quranic metadata, you can now create your own QuranRiwaya instance with your custom data. Simply prepare your data in the required format (Lists structure with SurahList, JuzList, PageList, etc.) and instantiate the library with QuranRiwaya.create(riwayaName, customMeta, customLists).

    All 40+ methods will work seamlessly with your data—including navigation (nextAyah, prevAyah), metadata queries (getAyahMeta, getSurahInfo), and advanced features (juz/page/ruku lookups). This opens up possibilities for researchers, developers working with regional mushaf standards, digital Quran applications targeting specific communities, and anyone needing Quranic metadata for specialized use cases.

    The library's architecture is designed to be data-agnostic—just plug in your data and everything works! For guidance on data structure requirements, see the API documentation or examine the existing riwaya implementations (Hafs, Qalun, Warsh) as reference examples.

    We are commited to expanding support for more riwayas and pagination systems in future releases. Meanwhile, we welcome contributions from the community to help build a richer ecosystem of Quranic metadata.

    • Surah: A chapter of the Quran. There are 114 chapters in Quran, each of different length.

    • Ayah: A verse number in the particular surah (chapter) of Quran. it is relative to the surah.

    • AyahId: Unique identifier for a verse in the Quran. It is a number that is the concatenation of the of sum ayahs of previous chapters of Quran and the verse number of particular Ayah. There are 6236 ayahs in Quran. AyahId is absolute, positive and is not relative to any surah.

    • Juz: A section of the Quran. There are 30 Juz (ajza) in Quran of roughly equal length. Most Juz' are named after the first word of the first verse of the Juz'. Read more here

    • Hizb: Each Juz' is divided into two Hizb (lit. "two groups", plural: Aḥzāb). Therefore, there are 60 Hizbs (ahzab) in the Quran.

    • Rub-el-Hizb/Maqra: Each Hizb is subdivided into four quarters called Maqra (lit. "reading"), making eight quarters per Juz. In Arabic, rub means 'one-fourth' or 'quarter', while ḥizb (plural aḥzāb) translates to 'a group'. There are 240 Maqras in the Quran. In most mushafs it is noted by symbol in the shape of an octagram, represented as two overlapping squares ۞. Read more here

    • Thumun al-Hizb: Specific to Qalun riwaya, each Hizb is further divided into eight equal parts called Thumun al-Hizb (lit. "one-eighth of a Hizb"). This results in a total of 480 Thumun al-Hizbs in the Quran. This subdivision allows for more granular reading and recitation segments, facilitating easier memorization and study. Read more here

    • Manzil: For the convenience of those who read the Quran in a week the text may be divided into seven portions. Each portion is called a Manzil. There are 7 Manzil in Quran. Read more here

    • Page: A section of the Quran that contains 15 lines (Madina mushaf)(depends on the mushaf).

    • Saajdah: Special ayahs that require reader to prostrate. There are 15 of them in Quran.

    • Ruku: (paragraph) is a group of related verses in a Surah. The end of a Ruku’ is marked by the Arabic letter ﻉ in superscript. There are 558 Rukus in the Quran. These are logical sections according to similar theme/objective or meaning. The bigger Surahs have been split into a number of Rukus, so that we would recognize when to do Ruku' (bowing) in Salat without interrupting a proceeding subject of the Quran. Additionally, on the margins of the Quran, usually three figures are written with ﻉ. The top figure shows the number of Rukus completed in that Surah. The middle figure shows the number of Ayats in the Ruku just completed. The bottom figure shows the number of Rukus completed in that Juz.

    • Qira'at (Recitations) and Riwayat (Narrations): The Quran has been transmitted through different authentic modes of recitation, known as Qira'at. There are ten recognized Qira'at, each named after a prominent reciter (Qari). Within each Qira'at, there are multiple Riwayat (narrations) - the chains of transmission through which these recitations were preserved. The most widely used today is the Hafs from 'Asim narration, which is used throughout most of the Muslim world and forms the basis for all visualizations on this website. Other well-known narrations include Warsh from Nafi' (common in North and West Africa) and Qalun from Nafi' (used in parts of Africa). While the variations between these narrations are minor (mostly involving pronunciation, elongation, or slight differences in word forms), they can occasionally affect verse counts and word statistics. Read more here

    You can find some examples here and souce code for them here

    • Koran-Center - Powerful and feature rich web application for reading and studying the Holy Quran.
    • Visual Quran - Interactive platform with visualizations and insights into Quran's structure.

    Demo image

    Quran-Meta is 100% unit test covered and moreover data is cross checked with other apis to guarantee absolute correctness.

    One can run pnpx jiti examples/data-check to run suite of validation tests against the following data sources

    There are some differences with KFQC data in page numbering, due to variations between different mushafs. We plan to address these differences in future updates by supporting multiple page numbering systems of different mushafs (15 line, 16 line and etc).

    Any suggestion to further improve this are welcome.

    Here you can find the following
    Source code in typescript TS
    Javascript code autotranspiled from TS as ES Next ESNext
    Javascript code autotranspiled from TS as CJS ES5+CommonJS
    Distributions of library as
    ESM for use with modern bundlers like webpack 2 or Rollup and for direct imports in modern browsers via <script type="module"> ES5+ESM
    IIFE for use with classic browsers via <script> IIFE

    This software is distributed under MIT license.

    Settings

    Member Visibility

    On This Page

    Quran Meta