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

linker

v0.0.6

Published

A solution to NYU's linker problem in Operating Systems class.

Downloads

11

Readme

  • (I) an immediate operand, which is unchanged;
  • (A) an absolute address, which is unchanged;
  • (R) a relative address, which is relocated;
  • (E) an external address, which is resolved
    • look at the last 3 digits of the number that follows E and it will tell you where else it is used.
    • follow until you hit 777

All absolute addresses need to be put into the memory map & are not mutable

companies will be created a community will be created with pizza and trophies we will be a gatekeeper

  1. Go through first lines of modules (every 3 lines) and create symbol table
  2. Create the memory map

error's I'm not handling

  • (√) If a symbol is multiply defined, print an error message and use the value given in the first definition.
  • (√) If a symbol is used but not defined, print an error message and use the value zero.
  • (√) If a symbol is defined but not used, print a warning message and continue.
  • (√) If an address appearing in a definition exceeds the size of the module, print an error message and treat the address given as 0 (relative).
  • (√) If an address appearing in a use list exceeds the size of the module, print an error message and treat the address as the sentinel ending the list.
  • (√) If an address on a use list is not type E, print an error message and treat the address as type E.
  • If a type E address is not on a use list, print an error message and treat the address as type I.

count which module you're in

count which of the 3 parts of a module you're in

count how long that part is

TODO

  • Fix issue's with line 69 in linker.js
  • Add support for last error type
  • Add to npm
  • Translate to Python