i installed couple of packages 'project a' (e.g bootstrap) assuming available subsequent projects. when new meteor project 'project b' created, meteor list showed default packages. assumption meteor packages ruby gems available globally incorrect. work offline every , then, there way can manually copy/re-use installed packages?
yes similar gems. packages installed in ~/.meteor/packages, in precompiled form. can installed globally way.
when add package project copy package there build-cache directory hidden in .meteor directory of project.
to install package locally can re-use have clone github repository of package , place output in /packages directory of meteor app.
for example bootstrap, twbs:bootstrap clone reposistory: https://github.com/twbs/bootstrap, directory /packages/twbs:bootstrap (name doesn't matter if defined in package.js file on repository.
in general can re-use package without hassle of adding in manually so. it's better use global packages kept date.
the trouble comes being offline. if use local package guaranteed work. whereas global ones can give bit of trouble once in while when try add package in meteor tries check package date, npm packages involved package.
to keep short if added package in using meteor add twbs:bootstrap should able add project using same command. if keep packages & meteor date.
Comments
Post a Comment