how can support these npm/ember addon scenarios?
- developers build ember addon , use build ember application b uses local package
- developers builds b installing our nexus npm integration repository
- build system builds ember addon installing our nexus npm release repository
maven
- developer desktop builds install packages local repo used later in build.
- build system builds deploy packages our internal shared repo used developers don't need build all
npm
- build system builds can use npm publish --registry http://ourrepo/nexus/.... publish private registry
- develop desktop builds do????
we use dependsonme relative paths requires setup kind of rule builds work 1 way locally , on build machine.
while possible, hope there's more elegant solution making happen.
can have developers generate packages go local npm cache later use , if can point me documentation?
related
because use maven front end plugin manage npm , ember can encapsulate additional npm module (in case ember addon) maven artifact , make use of maven dependency management our various scenarios
ember add on module
- add 'npm pack' generate local package in npm repository (in our case root/target/tmp/.npm//)
- add assembly generate tar.gz containing tar file (a little silly) , attach module artifact (type: tar.gz, classifer: ember-addon)
client module
- add maven-dependency-plugin unpack unpacks addon module's tar.gz classifier: ember-addon target/ember-addons prior npm execution module
- modify package.json use local dependency "our-addon" : "file:../../target/ember-addons///package.tgz"
if user builds ember , client, addon module build placing artifact in local maven repository. client module unpacks local repository , pulls node_modules via npm ember build process.
if user builds client, client module fetches addon artifact our nexus repository prior unpack , use phases.
Comments
Post a Comment