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

locator-react

v0.1.0

Published

React template compiler for locator

Downloads

11

Readme

locator-react

Prototype of React template compiler for locator.

This component is a result of a hack to try to integrate Facebook's React framework with Locator component from Yahoo! to compile React's templates into YUI Modules that could be used on the server thru express and on the client thru YAF.

The beaufy of this is that you can still maintain the separation between your markup and your code, and most important, you will NOT need to download the transform component into the client side since all markup pieces (in a form of templates) are accesible on-demand thru YUI Loader.

Note: This is not production ready by any means.

Installation

Install using npm:

$ npm install locator-react

By installing the module in your express application folder, you should be able to use it thru Locator.

Usage

Integration with locator on the server side

Normally, you will plug the locator plugin exposed by locator-react into the locator instance, and locator will be able to analyze every file in your express app, and it will compile any *.react or *.jsx into a YUI module that can be used thru express-yui for example. The example below describes how to use the yui plugin with locator:

var Locator = require('locator'),
    LocatorReact = require('locator-react'),
    loc = new Locator();

// using locator-react yui plugin
loc.plug(LocatorReact.yui());

// walking the filesystem for an express app
loc.parseBundle(__dirname, {});

Server side with express and express-yui

A more complete example will be:

/*jslint node:true, nomen: true*/

'use strict';

var express = require('express'),
    YUI = require('express-yui'),
    Locator = require('locator'),
    LocatorReact = require('locator-react'),
    app = express(),
    loc;

// custom view engine to rely on yui templates
app.set('view', app.yui.view({
    // defaultLayout: 'templates/layouts/index' // optional layout
}));

// serving static yui modules
app.use(YUI.static());

// creating a page with YUI embeded
app.get('/bar', YUI.expose(), function (req, res, next) {
    res.render('templates/bar', {
        tagline: 'testing with some data for template bar'
    });
});

// locator initialiation
loc = new Locator({
    buildDirectory: 'build'
});

loc.plug(LocatorReact.yui())
    .plug(app.yui.plugin({
        registerGroup: true,
        registerServerModules: true
    }))
    .parseBundle(__dirname, {}).then(function () {

        // listening for traffic only after locator finishes the walking process
        app.listen(3000, function () {
            console.log("Server listening on port 3000");
        });

    });

Client side with yui

On the client side, any React template will be accessible as well thru yui as a regular yui module. Here is an example:

app.yui.use('<name-of-app>-templates-bar', function (Y) {

    Y.Template._cache['<name-of-app>-templates-bar']({
        tagline: 'testing with some data for template bar'
    }, Y.one('#container'));

});

In the example above, the <name-of-app> is the name specified in the package.json for your express application, and the template bar.react will be refreshed under the #container selector.

note: in the near future, Y.Template.render() will be the formal API instead of using the _cache object, which is protected.

License

(The MIT License)

Copyright (c) 2013 Caridy Patino <[email protected]>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.