I understand that npm link would give me a 'live' version of my dependent module, but this might not be what I want, and AFAICT is not supported by I commented on my use cases and rationale for my hopes as comments here: https://gist.github.com/branneman/8048520#gistcomment-1567153 and https://gist.github.com/branneman/8048520#gistcomment-1567162 This is likely a separate issue so I can make a case if deemed so, but @kossnocorp's solution (which is very similar to what I use) fails on [email protected] when trying to shrinkwrap (doesn't on [email protected]) because the symlink is an "extraneous dependency".Not sure how to work around that yet or if that is a bug.There is also the suggestion of using preinstall: "npm install sub-module- is run, but I don't know how much attention @iarna has given to local dependencies on her work thus far.
Lightweight and simple OPDS server for the home use Tiny OPDS is a lightweight, simple OPDS server for Windows, written on C#. Just copy executable to the folder with read/write access (for example, to the C:\Users\User\Desktop (or /home/user/tinyopds), run the application, select your "book storage", i.e.
folder with epub and fb2 books (files may be stored to archive(s)) and press "Start scanning" button.
It sounds interesting but I reckon that it is based on the module versions and not on the content.
So if the version sub-module version is not incremented the content is not synchronized. I was hoping for something like Is there a link where the new dependency management of [email protected] is described?
The Node module loader would have to change to support this feature, and while the module resolution and loading algorithm is looking less locked down now than it has in the past (thanks to io.js), it seems pretty unlikely that the Node core team is going to want to make Node @othiym23 Thanks that explanation makes a lot of since.
And yeah I just found linklocal it seems to suit my needs pretty well.Native add-ons should include 'win_delay_load_hook': 'false' in their to disable this feature if they experience problems .(Bert Belder) #1433 * Governance: - Rod Vagg (@rvagg) was added to the Technical Committee (TC) - Jeremiah Senkpiel (@Fishrock123) was added to the Technical Committee (TC) I came across this thread after having the same issue.Just was really confusing at first because everything I had read up until your comment made it seem as if PR-URL: #1532 Notable Changes: * crypto: significantly reduced memory usage for TLS (Fedor Indutny & Сковорода Никита Андреевич) #1529 * net: socket.connect() now accepts a 'lookup' option for a custom DNS resolution mechanism, defaults to dns.lookup() (Evan Lucas) #1505 * npm: Upgrade npm to 2.9.0.See the v2.8.4 and v2.9.0 release notes for details.That resolved our problems except the issue during deployment described above (currently we work around that by deleting What about setting up your NODE_PATH in production so that it searches all of your submodule roots?