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

g2p_mapper

v2.1.5

Published

Map genome to protein coordinates and back

Readme

g2p_mapper

A zero-dependency TypeScript library for mapping genome positions to protein/transcript positions and vice versa. Works with GFF3-style features and handles both forward and reverse strand genes, CDS phase offsets, and duplicate CDS deduplication.

Install

npm install g2p_mapper

Usage

Pass a transcript feature (with CDS subfeatures) to genomeToTranscriptSeqMapping:

import { genomeToTranscriptSeqMapping } from 'g2p_mapper'

const { g2p, p2g, p2gCodon, refName, strand } =
  genomeToTranscriptSeqMapping(feature)

// g2p: Record<number, number>        — genome position → protein position
// p2g: Record<number, number>        — protein position → first genome position
//                                      of the codon (in transcription order)
// p2gCodon: Record<number, number[]> — protein position → all genome positions
//                                      of the codon, in transcription order;
//                                      correctly handles codons that span an
//                                      exon boundary

The input feature should match the Feat interface:

interface Feat {
  refName: string // chromosome/contig name (required)
  start: number // 0-based (required)
  end: number // 0-based, half-open (required)
  type?: string // e.g. 'mRNA'; CDS children must have type === 'CDS'
  strand?: number // 1 (forward) or -1 (reverse); required on the parent
  phase?: number // CDS phase (0, 1, or 2); only the first CDS's phase is consulted
  subfeatures?: Feat[] // should contain CDS children
}

All coordinates are 0-based and half-open ([start, end)).

Worked example

const ret = genomeToTranscriptSeqMapping({
  refName: 'chr1',
  start: 0,
  end: 6,
  strand: 1,
  subfeatures: [
    { refName: 'chr1', start: 0, end: 6, type: 'CDS', strand: 1, phase: 0 },
  ],
})
// ret.g2p      => { 0: 0, 1: 0, 2: 0, 3: 1, 4: 1, 5: 1 }
// ret.p2g      => { 0: 0, 1: 3 }                // first genome pos per codon
// ret.p2gCodon => { 0: [0, 1, 2], 1: [3, 4, 5] } // all positions, transcription order

For reverse-strand features, p2gCodon lists positions in transcription order (descending genomic coordinates). On a reverse-strand CDS [0, 6) the same codons become { 0: [5, 4, 3], 1: [2, 1, 0] }.

Looking up codon ranges

getCodonRanges returns the genomic ranges covering a codon. It correctly handles codons that span an exon boundary by returning multiple ranges.

import { getCodonRanges } from 'g2p_mapper'

// Returns [start, end)[] sorted ascending, or undefined if the protein
// position is unknown.
const ranges = getCodonRanges(p2gCodon, proteinPos)

getCodonRange is a faster single-range alternative kept for backwards compatibility. It assumes the codon's three bases are contiguous in genome coordinates, so it returns wrong ranges for codons that span an exon boundary or for split codons at a phase-shifted CDS start (phase != 0). Prefer getCodonRanges for new code.

import { getCodonRange } from 'g2p_mapper'

// Returns a single [start, end) interval, or undefined.
const range = getCodonRange(p2g, proteinPos, strand)

See also

  • https://github.com/cmdcolin/g2p_mapper_cli — CLI wrapper for this library
  • https://github.com/cmdcolin/interproscan2genome — maps InterProScan protein annotations back to genome coordinates
  • https://github.com/cmdcolin/jbrowse-plugin-protein3d - our plugin for mapping 3-D protein structure positions to the genome
  • https://github.com/GMOD/jbrowse-plugin-msaview - our plugin for mapping MSA sequence positions to the genome

Footnote

This package makes various assumptions about the biology, specifically simple 3-letter codon translation. This assumption may not be valid in all circumstances (biology breaks the rules constantly). Make sure to validate these assumptions for your application

Publishing

Trusted publishing via GitHub Actions.

pnpm version patch  # or minor/major