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

swedn

v0.0.1

Published

white space sensitive edn

Downloads

1

Readme

swedn

#What is this? sweet expressions for EDN. Lets just jump into an example:

;swedn
:cats
  :cordelia
    :name "cordelia" 
    :age 6
  :tofu 4
  :margaret 3
:dogs
  :schnitzel
    :favorite-toys :ball1 :ball2 :ball3 
    :friends [:margaret] 
    :color {:hair [:black :tan] :eyes #myApp/eyeColor :brown}

;edn
{:cats {
   :cordelia {
       :name "cordelia"
       :age 6}
   :tofu 4
   :margaret 3}
 :dogs {
   :schnitzel {
     :favorite-toys [:ball1 :ball2 :ball3]
     :friends [:margaret]
     :color {:hair [:black :tan] :eyes #myApp/eyeColor :brown}}}}

Hopefully from the above it is apparent that we are implicitly in a Map as (for me at least) this is my most common use-case for EDN.

If we find a single item after a key we assume it represents itself.

If we find more than 1 we assume it is a vector (this means if we want a vector of one item as the value we need to explicitly do [item]).

If we explicitly want a list we need to express that, the same goes for sets.

All other normal edn values and parsing apply.

If we want an "inline map" it needs to be explicit e.g. {:key val}

If you want an ordered map you can accomplish this by starting in a vector (this is useful for a DSL for instance)

;swedn
[define x
    y z
 define z
    x y]
    
;edn
[{define [x {y z}]} 
 {define [z {x y}]}]