Nano.php has been deprecated. It's replaced by the Lum.php set of libraries. These are available in Composer, and are handled differently from Nano.php.
If you want to migrate your code, you will need to find the new class name
and update any code refering to the old class. Otherwise, Nano.php v5 still
exists in the nano5 branch of this repository.
You can find all the repositories at Github. Additionally, I will slowly be adding documentation on a simple webpage.
A migration from Nano.php to Lum.php is cannot be fully automated, however
a great deal of it can be assisted using the nano2lum.php script included
in this repo.
I hope I have support for all of the new classes in it. I'm still testing it, and will update it if it's missing anything.
In addition to searching for changes to your PHP files, it can also look for references to the old Nano.js and replace them with the new Lum.js names.
These example are non-destructive, they won't actually change the files it
will simply make a report of what files WOULD be changed if you added
the -C option to the command line.
php nano2lum.php -d /path/to/your/app -e vendor -p php > report.yaml
The output file would have a list of all files that would be modified,
as well as a list of any Lum libraries you'd need to add to your composer.json
file, and a list of any bootstrap files (i.e. files that used to load the
lib/nano/init.php which will need to be manually updated in many cases.)
You can make the report more verbose by adding -v to the command line.
You can make it really verbose by adding -vv to the command line.
Making a report for your JS files is just as simple:
php nano2lum.php -d /path/to/your/app -e node_modules -j js > report.yaml
The report would be very similar to the PHP one, except there is no library usage or bootstrap information for the JS classes.
You could combine the two into a single call:
php nano2lum.php -d /path/to/your/app -e vendor -e node_modules -p php -j js > report.yaml
For additional features of the nano2lum.php script, run it without any
parameters and it will display it's built-in usage information.
Also if you don't have the PHP yaml extension installed, it will use
JSON output instead of Yaml. You can force JSON output by passing -J.
I think for these reports Yaml is easier to read which is why it's the default.
For any of the above, if you add the -C command the script will actually
change each of the files. It does not make backups, as I'm assuming you are
using a version control system and would be smart enough to only run this
script on your codebase in a development branch with all local changes
committed already. Be careful when running any kind of script that can change
your codebase. Make sure your work is committed first!
Timothy Totten [email protected]