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

lazorse-nesting

v0.1.2

Published

Flexible nested resource support for Lazorse

Downloads

3

Readme

Lazorse-nesting

horse in a nest

This module can be @includeed into a Lazorse application to enable client-driven inlining of named resources. By client-driven, we mean that the client specifies a list of related resources as part of the request, and this extension takes care of inlining those resources into the response data.

How it works

The client to specifies keys they would like to have inlined into their response using a query parameter (inline by default). When those keys are seen in the response data, and the value of those keys looks like a URL path (such as the ones generated by the builtin @link helper), the value will be replaced with the response data of an internally dispatched request against that path.

To see how this looks in practice, check out this test.