now my question is : can i make that customisation inside my project, to have no risk to loose it, rather than in …/.meteor/ which seems a bit tricky ?
thanks i tried but… that package do not contain what i need to modify
( plus i had a message in terminal “typ:accounts-ldap upgraded from 1.0.1 to 1.1.0” and a test made the app crash with “SizeLimitExceededError: Size Limit Exceeded at messageCallback (~/.meteor/packages/typ_ldapjs/.0.7.3…” )
From what you’re saying, it sounds like you want to get access to the version of the package you have installed.
Unfortunately, the package you’re looking at does not have any releases, nor are there any branches which might correspond to earlier releases. That means you’ll need to identify the commit which corresponds to the release you’ve got.
You can inspect the commits from this link. Clicking on a commit id (for example adfb5ee) will take you to a screen where you can “Browse Files”. Hopefully, you’ll be able to identify your version with a little investigating.
Once you’ve identified the commit id you need, go back to your packages/ folder and cd into the package you cloned. From there you can checkout the commit you need and work from there.
now i succeed to reinstall my sources on a meteor 1.7.0.5 new bare project, and on a 1.6.1.4 too
both are using ~/.meteor/packages/typ_ldapjs/.0.7.3/…
i do not understand why in that folder the files structure do not looks like etyp/meteor-accounts-ldap at all, that looks like joyent/node-ldapjs which seems to be an unrelated package
i still would love if there is a way to copy a subfolder from my own ~/.meteor/packages/… to my ~/project/packages/ so i can make my modification permanent without more investigation