Hi, So I was wondering, what approaches can/should be taken if you're developing both a library and an app at the same time. Our app is a UI based app, running in the browser, but there's an underlying library that we leverage that includes some of our basic UI components. This library changes infrequently but it does change.
We're very much a bunch of guys who have done server side java development for a while, and now have a need to do some UI development. Someone wrapped this library in a maven build, which somewhat works. Ideally what we want is that when a change is made to the library, CI runs and deploys the artifact somewhere. This part works fine. However, we also have cases where you are doing local development and don't want to publish your changes until you're sure they work in the app. In either case, we're going to pushing out something with a version #, and that version # need not change with every commit. Will npm poll the repository still for changes? Currently all of our builds are based on npm link. Looking at how it works, I'm thinking its not a good idea since it creates a global link. We've had cases where code leaked into the wrong branch because of the global link in our CI. Any tips, pointers, I'm sure I sound a bit confused. ;-) John -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/2577fc26-2fc0-479a-99e0-4ce4b88fdfd2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
