Skip to content

fix(qiankun-plugin): 修复本地研发时热更新报错 #10165

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Dec 29, 2022

Conversation

HiLanXiao
Copy link
Contributor

本地研发时设置__QIANKUN_DEVELOPMENT__ 为true

@vercel
Copy link

vercel bot commented Dec 28, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Updated
umi ⬜️ Ignored (Inspect) Dec 29, 2022 at 3:02AM (UTC)

@codecov
Copy link

codecov bot commented Dec 28, 2022

Codecov Report

Base: 29.88% // Head: 29.88% // No change to project coverage 👍

Coverage data is based on head (957c00a) compared to base (7ca6a37).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           master   #10165   +/-   ##
=======================================
  Coverage   29.88%   29.88%           
=======================================
  Files         432      432           
  Lines       12409    12409           
  Branches     2974     2974           
=======================================
  Hits         3708     3708           
  Misses       8135     8135           
  Partials      566      566           
Impacted Files Coverage Δ
packages/plugins/src/qiankun/slave.ts 0.00% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@sorrycc sorrycc merged commit 6018165 into umijs:master Dec 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants