# icestark-app

> icestark micro-frontends solution, APIs used by sub-application. [icestark docs](https://ice-lab.github.io/icestark/).

[![NPM version](https://img.shields.io/npm/v/@ice/stark-app.svg?style=flat)](https://npmjs.org/package/@ice/stark-app) [![Package Quality](https://npm.packagequality.com/shield/@ice%2Fstark-app.svg)](https://packagequality.com/#?package=@ice%2Fstark-app) [![build status](https://img.shields.io/travis/ice-lab/icestark.svg?style=flat-square)](https://travis-ci.org/ice-lab/icestark) [![Test coverage](https://img.shields.io/codecov/c/github/ice-lab/icestark.svg?style=flat-square)](https://codecov.io/gh/ice-lab/icestark) [![NPM downloads](http://img.shields.io/npm/dm/@ice/stark-app.svg?style=flat)](https://npmjs.org/package/@ice/stark-app) [![David deps](https://img.shields.io/david/ice-lab/icestark.svg?style=flat-square)](https://david-dm.org/ice-lab/icestark)

## Installation

```bash
npm install @ice/stark-app --save
```

#### Why is the sub-application API to be drawn separately `@ice/stark-app`?

- The APIs used by sub-applications are very stable and do not have to be updated frequently with the main package
- Sub-application APIs are more compatible and support non-relay systems

#### Compatibility

`icestark-app` supports all major browsers and supports all popular frameworks such as react, vue, angular, jQuery, etc.

## Contributors

Feel free to report any questions as an [issue](https://github.com/ice-lab/icestark/issues/new), we'd love to have your helping hand on `icestark`.

If you're interested in `icestark`, see [CONTRIBUTING.md](https://github.com/alibaba/ice/blob/master/.github/CONTRIBUTING.md) for more information to learn how to get started.

## License

[MIT](LICENSE)