When doing local development of a ropm package (i.e. ropm install ../some-local-package), anytime you make a chance to that package, you need to run ropm install again to copy the files to the proper roku_modules folders. The downside of ropm install is that it will attempt to download any missing dependencies from the registry, which takes some time even when nothing has changed.
This PR adds a new command, ropm copy, which skips the registry check. The general workflow is as follows:
Perform a full install: ropm install ../some-local-package
Anytime you make changes to ../some-local-package, run ropm copy, which will be faster than ropm install.
When doing local development of a ropm package (i.e.
ropm install ../some-local-package), anytime you make a chance to that package, you need to runropm installagain to copy the files to the properroku_modulesfolders. The downside ofropm installis that it will attempt to download any missing dependencies from the registry, which takes some time even when nothing has changed.This PR adds a new command,
ropm copy, which skips the registry check. The general workflow is as follows:ropm install ../some-local-package../some-local-package, runropm copy, which will be faster thanropm install.