I have already tested the package by using meteor add package-name into an existing app, and it works fine, but I’d like to add a feature to it…
What is the recommended way of now editing, debugging, then repackaging an existing package as a private version?
Is the process documented somewhere?
You create a directory called packages and clone the package you’d like to modify into it. Meteor would then start reading from this local fork instead of its atmosphere counter part. You can then modify it however you want and then create the PR back into the original package.
Thanks
I found the main repo veliovgroup/Meteor-Files, but cannot see where to clone the ostrio:files 2.3.3 package from…
If you want to push your updates back to the original repository, you can go with a fork (Fork 169).
If you want to clone the repository and use it as a package, just clone it as a zip and place it where you need to use it (like @harry97 said).
Download ZIP under <> Code.
The repo is the package (plus some extra files and folders such as demo folders and github related files and folders such as docs, CODE_OF_CONDUCT which you don’t need to remove although you could.)
To make sure you use a local version of it in your Meteor app, you can increment the version number in package.js and check the version under app/.meteor/versions
I’ll give it a try and see how it goes, and let you know,
The best way would be to send a PR to original package. While PR is in review you can use local version of the package from /packages directory
To clone specific package version download it as archive from Releases section on GitHub
