nanopage icon indicating copy to clipboard operation
nanopage copied to clipboard

super handy utilities for traversing flat content state

Results 10 nanopage issues
Sort by recently updated
recently updated
newest added

*** ☝️ **Important announcement:** Greenkeeper will be saying goodbye πŸ‘‹ and passing the torch to Snyk on June 3rd, 2020! [Find out how to migrate to Snyk and more at...

greenkeeper

## Version **12.0.0** of **standard** was just published. Dependency standard Current Version 11.0.1 Type devDependency The version **12.0.0** is **not covered** by your **current version range**. If you don’t accept...

greenkeeper

Should just expose array methods, too! ``` .forEach() .filter() .reduce() .map() ```

Added all sorts of fun stuff here. - **Flat state** for files, no more `files` key in pages, but uses regex in the same way as `find`. - **Cleanup** to...

Allow a second argument into `page` to define a dynamic/fallback content entry. Example in context of `choo`: ```js var page = require('nanopage') var p = page(state.href, { source: `/bundles/${state.params.id}.json`, loaded:...

I've been trying to figure out an elegant way to support multiple image sizes with `hypha`, but perhaps there's an opportunity for `nanopage` to smooth this over. Is there any...

Potentially allow lookups for keys not formatted like a path. This is mainly for allowing edge-case arbitrary content (I've been doing this), for example your content object could be shaped...

enhancement

The new `pages` regex checks against a key named `url` to find children. This is fine when using with something like `hypha` as it defines a `url` key in each...

Curious if we need the wrapper function, instead of just directly exporting the class. Doing this would allow for easy extending: ```js var Nanopage = require('nanopage') class Page extends Nanopage...

Write a short essay about how state is great for apps, but kind of awkward for sites. Paths as object keys, etc…