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

choo-lazy-view

v2.0.0

Published

Lazily fetch view when needed

Downloads

27

Readme

choo-lazy-view

stability experimental npm version build status downloads js-standard-style

Lazily load views as the router invokes them. Works great with dynamic import or split-require but should work with any promise or callback API.

Usage

var lazy = require('choo-lazy-view')
var choo = require('choo')

var app = choo()

app.use(lazy)
app.route('/my-page', lazy(() => import('./views/my-page')))

module.exports = app.mount('body')

API

app.use(lazy)

Hook up lazy view manager to the app. The lazy view store detects jalla and bankai prefetch (_experimental_prefetch) behaviour so that server side rendering works just as you'd expect.

lazy(callback, loader?)

Accepts a callback and an optional loader view. The callback will be invoked when the view is called upon by the router. The callback, in turn, should load the required view and relay it's response (or error) back to the caller. This can be done either with a Promise or with a callback.

// using promise
app.route('/my-page', lazy(() => import('./views/my-page')))

// using a callback
app.route('/another-page', lazy(function (callback) {
  fetchView(function (err, view) {
    callback(err, view)
  })
}))

The second argument is optional and should be a function or a DOM node which will be displayed while loading. By default, the node used to mount the app in the DOM is used as loader (meaning the view remains unchanged while loading).

app.route('/a', lazy(
  () => import('./my-view'),
  (state, emit) => html`<body>Loading view…</body>`
))

During server side render, the store will expose the selector used by app.mount on the app state and use that as the fallback loader view. If you are not doing server side rendering and exposing the server side rendered state as initialState on the client, a loader view is required. Note: jalla does this automatically for you.

Events

Events are namespaced under lazy and emitted when loading views.

lazy:load(promise)

When fetching a view. The argument promise resolves to the loaded view.

lazy:success()

When the view has been fetched, before the app will render.

lazy:error(err)

When the view fails to load.

License

MIT