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

dsr-kv

v0.2.2

Published

De-Serialize keys or values in a stringified JSON object.

Downloads

13

Readme

dsr-kv

De-Serialize object keys or values in a stringified JSON object/data structure.

Installation

To get started, run the command:

npm install dsr-kv

[!NOTE] It doesn't deserialize the whole JSON string(as JSON.parse() would), instead just the keys or values(or both) of objects found in the JSON string.

Why?

While building lofo, as a step during the program's execution, I wanted to write an object literal to a file. The obvious solution was to JSON.stringify() the object first, then write it to the file but, the result of that approach was this issue, where Next.js would fail with an error: Unexpected object key type, when trying to read the "stringified" object. I concluded that the solution was to "deserialize" the object key first, then write to the file. It worked!

At the time, I had a minimal implementation of the idea(that worked), this package is just a "finished" version of that implementation.

Of note, is that the there is currently no implementation for deserialization of object values(only keys) as the use case for that is unclear for now...

Usage

import { dsr } from "dsr-kv"

const data = {
  hello: "world"
}

// Get JSON string;
const jsonString = JSON.stringify(data); // Output: '{"hello":"world"}'

// Deserialize object keys found in JSON string;
dsr(jsonString) // Output: '{hello:"world"}'