Node and Express Tips
calv.info
calv.info
This sounds like a maintenance nightmare when you start juggling lots of code.
A simpler solution might be to put your custom modules in node_modules (without symlinking) and then commit those to your source tree.
The main point that I wanted to get across was that it's worth structuring your packages in such a way that makes it easy for developers to write new modules without using a lot of relative paths in the file system. Node does this work already, so I like to take advantage of it.
git submodules are designed to solve this problem and do so very well, allowing each project that uses a shared module to include whatever version it pleases, yet allowing the project using the shared module to update/rollback to a newer/older version.
"[$NODE PATH exists] mostly for historic reasons. You are highly encouraged to place your dependencies locally in node_modules folders. They will be loaded faster, and more reliably."
http://nodejs.org/api/modules.html#modules_loading_from_the_...
> ...small shared library files that don't justify their own package.json...
Generating a package.json + dependencies is a 30 second job with npm init + npm install --save + npm link. I follow a similar pattern to you when developing inside a single module, where I start growing module saplings in a ./lib folder to spike on ideas without the overhead of totally decoupling from the parent, but as soon as you need to share that code around and put it into your $NODE_PATH, you've got to decouple it anyway, so really you're effectively 30 seconds worth of work away from creating a real module anyway, and thus you could do away with your custom $NODE_PATH.
I am sure you are a most upstanding, interesting, and funny fellow. I respect that you appear to possess a love of hats.
Despite my sincerest regards for your person and well being, I must say that the UI of your site is somewhat hard to use. I, and others like me, read the web as much from our small screen devices as we do from our big screens.
Your site, when viewed on an iPhone, has a large overlay at the bottom containing a photo of you wearing a hat and your name, and it takes up nearly 1/3 of the entire viewable screen. It makes reading the content of your site uncomfortable, and nigh impossible. This is at least the 2nd article from your site which I have had to avoid from Hacker News. This is disappointing, since having made the homepage several times indicates you are someone I might find interesting. As it stands, I am bereft of being able to discovering your thoughts and reflecting on them myself.
Please, consider a modification to your UI for those of us who only have small viewports with which to interact with the world.
And you're right, he is a hat connoisseur.
- I move between client and server fairly frequently, and AMD works in both via RequireJS.
- I often share code between client and server, eg, my current app has a shared models module that is augmented by the client and server-specific modules that import it.
I avoid adding methods by a string for the simple fact that JSHint warns about using [] rather than . wherever it can (I think the only time I use [] is for Express' badly named 'static' plugin - 'static' is a reserved word.
Following you on Twitter (I'm @mikemaccana). Hope to catch you about someday!
The shared code between client and server is definitely an interesting concept. I'd be interested to see some of your posts on how this ends up working!
Our app isn't grouped strictly into resources, though it's something we might be able to benefit from. Currently we use different pieces of middleware to load whatever items the route needs.