Yarn is currently the newest package management system for JavaScript, and also the default for Rails 5.1.
Has it been considered to be included in software collections?
Rails 5.1 is currently not in Software Collections and support for Yarn is since Rails 5.1.
You can however use NPM. I'm also not sure about Yarn being default for Rails.
http://edgeguides.rubyonrails.org/5_1_release_notes.html#yarn-support
Related
I have a Laravel 5.4 project (web application), it's a huge product. I want to add some well known packages like error logging and debugging. Is there any simple way to update the Laravel from 5.4 to 5.5 or 5.6 without affecting the things what was already done? How can I do this?
You should never upgrade your production environment directly without testing. It would be better to set up a staging environment and test the upgrade there. If you don't have any problems there, consider upgrading the production environment.
If you want to know all changes from older versions to newer versions, check the upgrade guides in order:
https://laravel.com/docs/5.5/upgrade
https://laravel.com/docs/5.6/upgrade
https://laravel.com/docs/5.7/upgrade
I have a large project running on Laravel 4.2 and now I would like to upgrade it to the latest release (5.4)
On the upgrading guide I can see the steps to upgrade from each release to the next one, but the 4.2 to 5.0 requires a fresh install. Hence the question: should I install 5.4 (and fix problems) or 5.0 (running each upgrade)?
I'm possibily using any Laravel functionality, and have organized repositories for my own custom methods; I also need to maintain the database. I need to upgrade because I would like to use event bradcasting with Laravel Echo.
Thanks
To those looking for an answer: update directly to latest version, then fix changes along the way.
Explanation:
At first I tried to upgrade version by version; it was a pain. Every single vendor had different packages for each version and that caused issues even before correcting the code. I couldn't start fixing my code because the installation requirements of the vendors were failing at a certain point of the upgrade process.
Upgrading directly to latest version requires the correction of many things, but at least those are only related to your code. In my case I had to remove Sentry (authentication), Laravel OAuth, and some others I don't remember in favor of some native packages which I hope will be maintained properly. The upside of this approach is that once you have all the packages you need installed you can work directly on your code... which is what you have to do anyway.
I have an app built using the legacy 2.x (2.1.4 to be exact) version of CodeIgniter. Now I want to upgrade. How would I do that?
Or is it even possible and easy?
Upgrade first from 2.1.4 to 2.2.0 by replacing all files in the "system" folder and then use the tutorial on the official codeigniter site.
I haven't tried this but it seems logical.
I updated my CakePHP 3 project via composer. I use the cake app skeleton. After update, my app gave me error messages about deprecated session helper. I checked the cakephp/cakephp github repository and in /src/Controller folder there are files like ComponentRegistry.php what I do not have in my project.
I am confused. Why composer did not sync these?
You are using the development version of CakePHP 3.1. In such version, the Session helper was deprecated. I would recommend setting your project to only work with the stable releases.
I have an existing OpenShift Online app that I created with a Ruby 1.9 cartridge.
Now that the Ruby 2.0 cartridge is available I'd like to "upgrade" my app to use that, but I can't figure out how to do it.
I tried doing an 'rhc cartridge-add ruby-2.0 -a ' but it says the cartridge isn't available.
I created a sample rails 4/ruby 2.0 app in my OpenShift Online account so I know the cartridge exists, but for some reason my ruby 1.9 app doesn't know about it.
I'm hoping I don't have to create a whole new app and then migrate my code over, re-populate the database, modify the Gemfile, etc.
Has anyone tried to do this and had success? This will be a periodic task for me, upgrading ruby and rails as they become available. I've upgraded rails already and that mostly involved gem and Gemfile changes, but the ruby cartridge upgrade seems different.
I'm thinking this has to have been worked out. Otherwise, established production apps could never have their language cartridges upgraded...?
You can not remove or upgrade a web cartridge (the main cartridge for your application). You will have to create a new application with the upgraded cartridge that you want to use and migration your application over manually. You might be able to use the rhc snapshot save & rhc snapshot restore commands, but I'm not sure if that works between different versions of the same cartridge.