Workflow in developing an EnderJS library component
<p>I'm developing a code module that will become an Ender library component. I have the source in a /src directory (the component .js and an ender.js bridge file). As I develop the code, I want to test the code -- iteratively. Which requires that I build the actual ender.js library file. </p>

<p>The problem is that running the "ender" (bin) command</p>

<pre><code>$ ender build myComponent
</code></pre>

<p>expects the myComponent to be an npm installable/updatable module, located in ./node_moudules. But I want ender to build from the ./src directory. </p>

<p>I know the docs say that one can specify a relative path, as in:</p>

<pre><code>$ ender ../path/to/myComponent
</code></pre>

<p>but I can't quite get this to work.... I assume I need a package.json that refers to the source files, so, I create a /build directory and put a package.json in there that has very little info, just:</p>

<pre><code>{
    "ender": "../src/ender.js",
    "main": "../src/doml.js",
    "name": "doml",
}
</code></pre>

<p>("doml" is the name of my library component).</p>

<p>But when I try executing:</p>

<p>$ ender ./build/doml</p>

<p>I get the message:</p>

<pre><code>something went wrong install your packags!
</code></pre>

<p>which is generated by the install method of ender-js's ender.npm.js file. So... something is terribly amiss because I don't want npm to install anything, I want ender to build from source that I'm specifying.</p>

<p>Clearly I am confused... please help clarify for me how development workflow can or should be organized.</p>

<p>(please note, I wanted to create an ender-js tag for this question, but I don't have sufficient reputation on StackOverflow to create a new tag.)</p>
