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

nice-place-for-coding-parser

v0.0.1

Published

Parser for nice-place-for-coding

Downloads

4

Readme

nice-place-for-coding-parser

Parse .md files into structured data for nice-place-for-coding

Why bother?

Although .json or .yaml format can be used directly without creating a parser, Markdown has its advantages:

  • It's human-readable
  • It's also structurally defined (like other dedicated format)
  • It's fun
  • It's not that much of a trouble

Format Spec

A valid file should contain at least one place entry. Each place entry should be in this format:

* Place name : place address

```

Notes on place

from @name_of_recommender

```

Note:

  • Nothing else can exist in between the list item and the code block
  • English colon must be used to separate place name and address. Spaces are allowed before and after the colon
  • Any contents (expect lists, both ordered an un-ordered ones) can be added between 2 place entries (see ./test/data/more-than-one.md)

Usage

Install:

npm install nice-place-for-coding-parser

Use:

Parser = require 'nice-place-for-coding-parser'

parser = new Parser()

places = parser.parse 'Markdown source'

Parser output:

[
  {
    name: 'name of place',
    address: 'address of place',
    note: 'note',
    recommendedBy: 'who'
  },
  // Other places
]