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

sugar-json

v0.0.3

Published

JSON plugin for Sugar JS

Downloads

3

Readme

Sugar JSON

JSON plugin for Sugar JS

Usage

Unless you using Sugar in extended mode this plugin is pretty much useless.

See relevant parts of docs:

sugarjs.com/quickstart/#/ChoosingAMode

Do not use extended mode if you are developing a library or other form of middleware. This is due to both awareness of the global scope described above as well as potential conflicts with versioning if other versions of Sugar exist. Extended mode should only be used by end users.

sugarjs.com/docs/#/objectPrototype

If you're feeling adventurous (and you generally have control over the code in your project) you can force Sugar to extend Object.prototype at your own risk using the objectPrototype flag

sugarjs.com/extending

The decision to have a modified global state is one that the end user or team should be well aware of. Failing to do this leads to issues that can be difficult to track down.

tl;dr; using extend is dangerous for middleware and libraries, and extending objectPrototype is always dangerous

(don't tell people on stack overflow that you have done this unless you are very thick skinned)

Having said all that, if you are both adventurous, and in control, you can now easily convert from plain js objects to json strings and back with ease, in a chainable way...

Configure Sugar to extend prototypes, including Object.prototype

require('sugar').extend({
  objectPrototype: true
})

require('sugar-json')

... define an object ...

let obj = {cool: 'beans'}

... turn it into string, do some replacements, then turn it back to object ...

let res = obj.stringify().replace('a', 'i').replace('cool', 'human').objectify()

... test it out ...

console.log(res)
// -> { human: 'beins' }