ReedSun opened a new issue #3292:
URL: https://github.com/apache/incubator-weex/issues/3292
<!--
Thanks for using Weex. Github Issue is only used for bur report and please
follow the template to report the bug.
A good bug report should include the following information:
-->
<!-- Requirements: please go through this checklist before opening a new
issue
- * Review the documentation: https://weex.apache.org/index.html
- * Search for existing issues:
https://github.com/apache/incubator-weex/issues
- * Use the latest Weex release:
https://github.com/apache/incubator-weex/releases -->
## Describe the bug
<!-- A clear and concise description of what the bug is. -->
When the device's system is Android 5.1, if
[he](https://github.com/mathiasbynens/he) is imported, even if it is not used,
the Weex page will be stuck in the loading state and cannot be rendered in only
production environment(uglify and mangle). In the development environment,
everything is normal.
## To Reproduce
<!-- Steps to reproduce the behavior. Include a MCVE using
http://dotwe.org/vue , crash stacktrace or share your app project. Please
follow the guidelines for providing a MCVE: https://stackoverflow.com/help/mcve
-->
First, install `he`.
```
npm i he
```
Then, import it.
```
<template>
...
</template>
<script>
import he from 'he'
</script>
```
Finally, run `npm run build`, and the bug will appear.
## Environment
* Device: 魅族 魅蓝2
* OS: Android 5.1
* Version 28
* Build from source yes
## Expected behavior
<!-- A clear and concise description of what you expected to happen. -->
render normal
## Screenshots
<!-- If applicable, add screenshots to help explain your problem. -->
## Additional context
<!-- Add any other context about the problem here.-->
Maybe this problem has something to do with #2563 #2616 #2519 #2213
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
