Package Exports
- nanomap
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (nanomap) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
nanomap 
Functionally map data into stateful nanocomponents.
Usage
var Nanomap = require('nanocomponent/map')
var YoutubeComponent = require('youtube-component')
var TwitterComponent = require('twitter-component')
var OEmbedComponent = require('oembed-component')
var simpleMapper = new Nanomap(opts, TwitterComponent)
// OR
var complexMapper = new Nanomap(opts, {
'video': YoutubeComponent,
'tweet': TwitterComponent,
...,
default: OEmbedComponent
})
[{
id: 'foo123',
opts: { color: 'blue' },
arguments: {an: 'arg'} // Non-array types passed in as the first argument
}].map(simpleMapper) // Array of rendered DOM nodes from homogeneous components
[{
id: 'foo123',
type: 'tweet',
arguments: ['tweet-url'] // component.render.apply(component, arguments)
}].map(complexMapper) // Array of rendered DOM nodes from a heterogeneous set of componentsInstallation
$ npm install nanomapAPI
Nanomap = require('nanomap)
Import Nanomap component class.
mapper = new Nanomap([opts], Component)
mapper = Nanomap([opts], { type: Component, [default: Component]})
Create a new mapper instance that will render data into component instances.
opts include:
{
gc: true // clean up unused instances when mapped over
}See examples for more details.