we use NODE_PATH=lib for this, but we had to write a wrapper around npm to
traverse the bundledDependencies so that your app modules are treated like
any others as far as dependencies go.
On Friday, 8 February 2013 17:24:39 UTC-8, Geerten van Meel wrote:
>
> Hi,
>
> I am working on an app and would like to access a component of my
> app simply using require('component') instead of require('./component')or
> worse
> require('./path/to/component.js'). I know that there are ways to achieve
> this by doing some hack regarding the node_modules folder, but I would like
> to ask whether there is a simple, elegant way to achieve this result (and
> not interfere with npm when deploying)?
>
> To summarize:
>
> - I would like to include an app component using require('component')instead
> of
> require('./path/to/component.js').
>
> - The components location should ideally be somewhere out of node_modules
> in order to not mess with npm.
>
> - NODE_PATH, thus process arguments should not be provided via the
> command line.
>
> Thank you for your time and suggestions!
>
> Geerten
>
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
