https://github.com/pmuellr/sample-npmish-project

a sample npm-ish project, built to explore how to run such a thing in AMD
https://github.com/pmuellr/sample-npmish-project

Last synced: about 1 month ago
JSON representation

a sample npm-ish project, built to explore how to run such a thing in AMD

• Host: GitHub
• URL: https://github.com/pmuellr/sample-npmish-project
• Owner: pmuellr
• Created: 2011-12-08T14:41:36.000Z (about 13 years ago)
• Default Branch: master
• Last Pushed: 2011-12-08T22:19:42.000Z (about 13 years ago)
• Last Synced: 2024-04-09T21:04:47.315Z (9 months ago)
• Language: JavaScript
• Homepage:
• Size: 93.8 KB
• Stars: 2
• Watchers: 2
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
sample-npmish-project

=====================

This project is a simple example of an npm-styled module layout for usage

in node.  I'm exploring how such a beast could be handled in an AMD-compatible

module system.

Here are the interesting bits:

* the main program - `sample.js`, loads two modules, `a`, and `b`, and then calls

the `run()` functions they export

* both `a` and `b` do a `require('c')`, and then run `c`'s `run()` function,

but the `c` modules they resolve to are

different - stored in the `node_modules` directory under `a` and `b`.

* `a`'s `c` module is resolved through a `package.json` file

* `b`'s `c` module is resolved via a `index.js` file

Both of the `c` modules print something different when run.  The output from

invoking

    node sample

should be

    in a/c

    in b/c

implementations

===============

browserify

----------

see: https://github.com/substack/node-browserify

to test, run:

    using/browserify/run.sh