Forced `noAuto` makes it difficult to transition from Font Awesome 4 to 5

Today, we heavily use <i class="fa fa-user"></i> throughout an application. It’s not feasible to update all usages at once. It will take some time to convert all usages to the new React component. However, by importing the react-fontawesome package, it forces noAuto throughout the rest of the application.

Is there a way to opt-out or can an escape hatch be added? Is there a reason react-fontawesome forces no auto?

Source referenced: https://github.com/FortAwesome/react-fontawesome/blob/9fe008e05c4308e1d12a53b7053998fc50f283e2/src/index.js#L4

[robmadole]

Hey there, we are working on version 5.1.0 of FA which will fix this issue. We’ll have a migration path that will mention this specifically. We expect to have this effort done soon (it’s priority #1 for our dev team)

[robmadole]

Hey @nelsonlaquet,

We currently have some pre-release candidates out (we are calling them 5.1.0) that address some of the issues that you’ve been having.

We are doing the work (and documentation) on the development branch:

https://github.com/FortAwesome/react-fontawesome/tree/development

Would you be willing to give this a try? Check out the UPGRADING.md for detailed instructions.

Also remember that since this is a pre-release you need to use NPM tag @prerelease like:

$ npm i --save @fortawesome/fontawesome-svg-core@prerelease

Please let us know how the upgrade goes and if you run into any problems. We are working hard to get the 5.1.0 release stabilized.