Material:
| import {b} from "./b.js"; | |
| import $ from "jquery"; | |
| export function a() { | |
| // ... | |
| } |
Creating npm packages which extend the functionality of Express apps has become a major thing we've been doing. There are several approaches we can take, from messing with the Express object prototypes, to creating a function in which an express app is passed in. After trying the former, I'm now a fan of the latter.
Extending the Express object prototypes has issues. The running Node.js process may have multiple versions of express, and in order to extend the prototypes you need to require('express'). This means that you might get a different express module instance than the one the main app is created from.
Both approaches suffer from extending something more than once. Similar to how there may be multiple version of express in the running Node.js process, there can also be multiple copies of the extension modules. If the app developer needs to rely on a different version of an Express ext
| /*jslint anon:true, sloppy:true, nomen:true*/ | |
| YUI.add('clickMojit', function(Y, NAME) { | |
| /** | |
| * The clickMojit module. | |
| * | |
| * @module clickMojit | |
| */ | |
| /** |
| #!/bin/sh -ex | |
| appname=${1:-hybrid} | |
| bldname=$appname-bld | |
| statdir=yahoo.application.$appname | |
| mojitodir=/Users/caridy/repo/mojito | |
| pwd | |
| mojito create app hybrid $appname |
| #!/usr/bin/env node | |
| var YUI = require("yui3").YUI; | |
| YUI({ | |
| debug: true | |
| }).use('node', 'io', function(Y) { | |
| //Messing with the main page.. | |
| Y.one('title').set('innerHTML', 'Digg News Headlines'); |