Skip to content
Use React components inside Angular
Branch: master
Clone or download
Latest commit f5abed6 May 16, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci fix all docs tests and run tests in CI (#100) Mar 17, 2019
.github add stale-bot configuration (#82) Jan 26, 2019
.vscode [Fabric] Add Dropdown component (#63) Dec 24, 2018
apps complete May 14, 2019
docs Update to fix after github move. Aug 10, 2018
libs Release version 0.6.5 May 16, 2019
test fix all docs tests and run tests in CI (#100) Mar 17, 2019
tools Upgrade all dependencies- Angular 6.1- TypeScript 2.9.2- office-ui-fa… Aug 2, 2018
.editorconfig chore: initial commit from @angular/cli Apr 4, 2018
.gitignore Removed ignoring docs in git (used for GitHub pages) Aug 2, 2018
.prettierrc prettier formatting Jul 13, 2018
CHANGELOG.md Release version 0.6.5 May 16, 2019
CODE_OF_CONDUCT.md Package upgrades, Prettier alignment (#38) Dec 1, 2018
CONTRIBUTING.md Package upgrades, Prettier alignment (#38) Dec 1, 2018
LICENSE Update to docs. Aug 16, 2018
README.md Add CircleCI build badge Jan 16, 2019
angular.json remove non-maintained projects Aug 2, 2018
nx.json Update to license/copyright on each lib file. Lint fixes. Aug 16, 2018
package-lock.json [Fabric] upgrade office-ui-fabric-react (#96) Mar 6, 2019
package.json remove legacy scripts (#113) Apr 10, 2019
tsconfig.json Allow wrapping any React component with an Angular one on-the-fly. (#106 Mar 30, 2019
tsconfig.packages.json [Panel] WIP Jun 28, 2018
tslint.json Package upgrades, Prettier alignment (#38) Dec 1, 2018
yarn.lock Package upgrades, Prettier alignment (#38) Dec 1, 2018

README.md

React support for Angular

npm version CircleCI

Industry trends, organizational pressures, and other factors can lead to mandates regarding the use of component libraries or migration from one technology to another. In the case of Office UI Fabric, where its use is required, the client must be written in React (there is no Angular component library for the latest version). Rewrite from Angular to React may be cost-prohibitive or ill advised for other reasons.

Use of Angular-React allows consuming any React elements, but specifically Office UI Fabric, within an Angular [2+] application. The library of wrappers for Office UI Fabric simplifies the use of these components with Angular. However, any React code can make use of the custom Angular-React renderer.

Quick links

@angular-react/fabric | Documentation, quick start, and guides | Demo | Contributing | StackBlitz Template | Office UI Fabric

Typical Use Cases

  • Use React component libraries with Angular
  • Incrementally rewrite an Angular application into React (moving from atomic/leaf nodes upward into full features/pages until the entire app is re-written)

Libraries

  • core: Includes the Renderer and supporting logic to render Angular components with React implementations as React components.
  • fabric: The light-weight Angular component wrappers that expose the Fabric React component API through common Angular components (including both imperative AND declarative syntax in many cases).

Roadmap

Initial work to prove the feasibility of adapting the Angular Renderer to output React managed components has concluded. We have moved beyond the initial simple Fabric components and expanded coverage to much of the available Office UI Fabric component library.

In the coming months we will continue to refine the component implementations as we use the angular-react core and fabric libraries in 2 real-world consumer facing production applications.

Getting started

See our Getting Started Guide if you're building your first project with Angular-React.

If you'd like to contribute, you must follow our contributing guidelines. You can look through the issues (which should be up-to-date on who is working on which features and which pieces are blocked) and make a comment.

You can’t perform that action at this time.