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

bitmark-parser-ts

v1.0.28

Published

A parser for Bitmark text

Downloads

47

Readme

Bitmark-parser-ts

A typescript bitmark-parser

On the fresh start (one time only)

$ npm install

Building the parser typescript source files:

$ npm run build-ts

To run with ts-node:

$ cd src
$ ts-node --esm call.ts tests/bug.bit

Building the Parcel bundle (with an example html)

Example HTML is the bundle-test.html, and the example main is main.ts. At the root of the package, do

$ npm run build-bundle

This command will build the html, js bunlde and map in the /dist directory.

You need to tweak dist/bundle-test.html -- the default src specification is src="/main.aa9d12ad.js". You will need to copy dist/* to your local apache www directory. But you will have to tweak this src value (location of the file) if you are copying the files to a different directory. For me the js files reside in the same direcory as the html, I just add '.' like this src="./main.aa9d12ad.js". Below is a generated bundle-test.html.

<!doctype html><!--[if lt IE 7]>      <html class="no-js lt-ie9 lt-ie8 lt-ie7" lang=""> <![endif]--><!--[if IE 7]>         <html class="no-js lt-ie9 lt-ie8" lang=""> <![endif]--><!--[if IE 8]>         <html class="no-js lt-ie9" lang=""> <![endif]--><!--[if gt IE 8]><!--><html class="no-js"><head><meta charset="utf-8"><meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"><title></title><meta name="description" content=""><meta name="viewport" content="width=device-width, initial-scale=1"><script src="./main.aa9d12ad.js" crossorigin></script></head><body> </body></html>

And you also need to tweak the map file location in the js file. It is usually specified at the end of the bundle js file. e.g. you see I added '.' before /main.aa9d12ad.js.map.

arse(n)}var r="[.conversation-right-1]\nYoo!\n",o="\n[.bot-action-response]\n===\n[!Ja, das weiss ich]\n[%A]\n[@reaction:celebrate]\n👍 Cool!\n===\n[!Das war mir nicht bewusst]\n[%B]\n😅\n[@reaction:like]\n===\nTHIS IS THE FOOTER\n",t=n(o);console.log(t);
},{"./src/index.ts":"B6dB"}]},{},["ZCfc"], null)
//# sourceMappingURL=./main.aa9d12ad.js.map

That's it. You copy the three files dist/bundle-test.html, dist/main.aa9d12ad.js, dist/main.aa9d12ad.js.map to your webserver document directory.