Not sure how many people are following the development of the v2 branch of uibuilder? This is a massive update and is taking much longer than I'd hoped. However, I think you will find the wait well worth while.
Anyway, after a bit of a break due to family and work commitments, please note that there is an updated development release that should be stable enough to play with.
It would be great if some people gave this version a hammering so that I can kill off any bugs I've not spotted
npm install TotallyInformation/node-red-contrib-uibuilde#v2 --save but note the breaking changes and limitations. Please don't try to use this with a version of Node.JS below 8.5.
Please note the changelog for breaking changes. There are a few of them I'm afraid though in many cases, you might not need to change anything. The change to the location of the socket.io client in your
index.html file is probably the one everyone needs to do. Just create a new flow to get the latest default front-end files
index.(html|js|css) so that you can see what has changed.
There are a few things that don't quite work fully as yet:
- Package management. You can see packages that are enabled but you can't yet add/remove them from the admin ui. Note that you no longer need any settings to tell uibuilder what packages to use! It will find any installed common packages ('vue', 'bootstrap', 'bootstrap-vue', 'jquery', 'moonjs', 'reactjs', 'riot', 'angular', 'picnic', 'umbrellajs') and automatically make them available. If you need to use something less common though, I'm afraid you will need to wait a bit longer. Of course, you can also let me know if you want anything adding to that list.
- File editing works from the admin UI - no more messing around trying to edit remote files on the server, Node-RED's standard ACE editor component is used. However, you can't yet create new files or delete any.
- The installed packages list isn't yet under the "Manage front-end libraries" button - that is just for convenience while I'm still changing it.
- Unfortunately, ExpressJS middleware isn't working at the moment. So if you rely on the middleware v1 made available, you will need to wait for a future dev release I'm afraid.