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

a2-memory-map

v1.0.4

Published

Database of Apple II memory addresses

Downloads

4

Readme

Apple II Memory Map

unit tests

This is the TypeScript binding to a database of Apple II special addresses intended to be used with language servers. The central element is the file map.json which maps addresses to a set of descriptive strings.

Map Records

The map records correspond to the interface

interface AddressInfo {
    brief: string | undefined,
    ctx: string | undefined,
    desc: string,
    label: string | undefined,
    note: string | undefined,
    subctx: string | undefined,
    type: string
}

The whole database is retrieved as a Map using

get_all() : Map<string,AddressInfo>

To get a single record use

get_one(addr: number): AddressInfo | undefined

The argument addr can range from -32767 to 65535. As an example get_one(0xfded) will give

{
  brief: 'Print character in A',
  desc: 'Invoke output routine whose address is in (56).  Usually prints character in A.',
  label: 'COUT',
  type: 'ROM routine'
}

AddressInfo Fields

  • brief: short description suitable for display in a selection box
  • ctx: notes on limiting context, such as hardware requirements, applicability to given language, etc.
  • desc: long description suitable for hovers
  • label: suggested assembler label
  • note: any other notes
  • subctx: notes on sub context, e.g., specific aspect of a language
  • type: data type (e.g. word) or operation type (e.g. ROM routine, soft switch)

Multi-context Records

The map.json file uses logic expressions to delineate information by context, e.g., ctx might have the value "Applesoft | Integer BASIC". The TypeScript interface provides a function to parse the logic and produce an array of records, with each element corresponding to a given context:

get_one_and_split(addr: number): Array<AddressInfo> | undefined

If there is no splitting of the ctx field, no other fields will be split. It is not required to use this function. If get_one is used instead, downstream will receive the logic expressions, which can be parsed in any manner desired.