Docs
Docs

Upgrade guide

Upgrading from version 3.0

To upgrade to version 3.1 follow the below steps:

Fresh install of version 3.1

Start by creating a new installation in a brand new folder and then copy your application's unique files from the old app to the new one. Make sure to read the rest of the upgrade guide before you start the upgrade process.

Laravel 5.2

A fresh Laravel 5.2 installation has been used in 3.1.
Every time Laravel releases a new version, we always reconstruct Laravel Angular Material Starter on a fresh installation. This means you always have the freshest Laravel code.

Angular 1.5

Angular has been updated to 1.5 which means you can now use components. Because of the efforts in Version 3.0, upgrading to Angular 1.5 should be as easy as:

  1. replacing .directive with .component
  2. returning an array instead of a function in the component definition

Make sure to read Angular's documentation on components.

📘

Not ready to use components?

You can keep on using your directives. Everything will work just fine.

EcmaScript 6 support!

Thanks to the Pull Request from @jadsalhani, we now have EcmaScript 6 support. Which means you can use some of the cool new features available in JavaScript. You can explore most of these features on babel's learn es2015 page.
This also means that you can use Classes for Component controllers.

👍

Your EcmaScript 6 code will be transpiled into EcmaScript 5 browser compliant code

Folder structure & generators

The folder structure has been slightly changed in order to accommodate the components architecture suggested by Angular 1.5 (and Angular 2).
We now have app/pages and app/components.
You could generate pages using artisan ng:page {page_name}.
Pages are meant to hold components together
Whereas components, can be generated by running artisan ng:component {component_name} and they are considered the building blocks of your front-end. Also the previous .definition.js file has been merged inside the .component.js file now.

Modified .gitignore

We stopped tracking public/js/, public/css and public/views. If you were using the generated files for deployment, you might need to include an additional step in your deployment routine.

👍

Version 3.1 Changelog

It is recommended that you carefully read the changelog for version 3.1.0 so you can get to know most of the new features included in version 3.1