-
-
Notifications
You must be signed in to change notification settings - Fork 605
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
vue2项目,热更新失效 #5445
Comments
把上述操作合并到一个 repo 里,然后贴下这个 repo 的链接吧。 |
Hello @luoriwusheng-xia, sorry we can't investigate the problem further without reproduction demo, please provide a repro demo by forking rspack-repro, or provide a minimal GitHub repository by yourself. Issues labeled by |
这里,这个仓库代码 https://gitee.com/luoriwusheng/vue-element-admin.git 里面的侧边操作栏的这个路由文件,改动代码,热更新就是失效的。 |
应该和这个有关,可以尝试一下 #5446 |
这个大概多久会发布一个新的版本 tag, issue里面的 版本号,好像是内部的版本号 |
@luoriwusheng-xia 可以提供以下你安装依赖的 lock 文件吗,你的仓库里没有,我这边没能复现你的问题 |
lock文件已提交, 原始仓库 忽略了lock文件。 |
放了一个gif动画,如果播放不了的话,可以留一个你的邮箱,我发你邮箱 |
感谢,mac 没能复现,最终在 windows native 下复现了。 测试矩阵: node:
- 18.19.0
rspack:
- 0.5.2
- 0.5.2-canary-d22f049-20240128005446 (2024.01.28 nightly)
shell:
- powershell
- pwsh
- cmd
terminal:
- windows terminal
- vscode terminal
command:
- `npm run dev`
- `./node_modules/.bin/rspack serve`
editor:
- vscode
- vim 均可以复现。 另外还测试了 mac + pwsh,无法复现。 另外经测试跟 #5398 这个 case 无关,相应变更无法修复该问题。 具体表现有点像没有触发 rebuild,不只是没有触发 hmr(手动刷新页面后还是老的代码)。 cc @h-a-n-a updaterspack build -w 也没有触发 rebuild |
bug 触发条件:
example: // changes on `aliased.js` doesn't emit rebuilding
console.log(require('@/aliased'))
// changes on `normal.js` emits rebuilding
console.log(require('./normal'))
// changes on next line emits rebuilding
console.log('entry') minimal repro: https://github.com/xc2/rspack-repro-rebuild-alias.git file dependencies |
This has been fixed in the latest release. |
thanks @Boshen |
thanks ! After verification in the warehouse, the issue has been fixed |
System Info
Details
在 vue2项目, 我改造 vue-element-admin , 发现热更新不生效, 但是改动 App.vue, 热更新是生效的。 改动 src/layout/index.vue
热更新失效
相关配置
Reproduce link
No response
Reproduce Steps
The text was updated successfully, but these errors were encountered: