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

patch-porter

v0.8.3

Published

.pchtxt porting tool

Downloads

9

Readme

patch-porter

A simple .pchtxt porting tool.

Usage

  1. Install Node.js, then install patch-porter using npm:

    npm install -g patch-porter
  2. Port your pchtxt:

    patch-porter --from=mainA --to=mainB --input=A.pchtxt --output=B.pchtxt
    • --comment: Add ported address as comment to the output file
    • --arch=arm64: Set the processor architecture for the NSO file (arm/arm64/none), default: arm64
  3. Done!

Tips

  • Please keep @flag offset_shift ... in your pchtxt to help patch-porter finding the correct address

  • If your pchtxt doesn't have @flag offset_shift 0x100, it means that the addresses in your pchtxt are not based on the NSO header offset.
    In this case, you need to decompress your NSO file using hactool, and disable NSO mode in patch-porter (--no-nso).

    hactool -t nso --uncompressed mainA.raw mainA
    hactool -t nso --uncompressed mainB.raw mainB
    patch-porter --from=mainA.raw --to=mainB.raw --input=A.pchtxt --output=B.pchtxt --no-nso
  • After porting, search for [x] in new pchtxt to find errors

  • patch-porter does not currently update the assembly code, so some patch may still need to be updated manually

Use in Node.js

import { promises as fs } from 'fs'
import { portPchtxt } from 'patch-porter'

let fileA = await fs.readFile('mainA')
let fileB = await fs.readFile('mainB')
let pchtxtA = await fs.readFile('A.pchtxt', 'utf8')

let pchtxtB = await portPchtxt(fileA, fileB, pchtxtA)

await fs.writeFile('B.pchtxt', pchtxtB)

Credits